We have a table that is showing a large amount of "reserved" space:
Rows: 4095513
Reserved 11255328 KB
Data: 1176296 KB
Index_size: 531240 KB
unused: 9547792 KB
(found wiht sp_spaceused)
We have only simple types in this table... no ntext or blobs or
anything.
Just int, smalldatetime, varchar(50) etc. (only 10 fields)
So our data and indices come to about 1.6 GB, but "unused" space is 9.1
GB.
We are running out of drive space...why would it reserve so much space
for this table?"cmay" <cmay@.walshgroup.com> wrote in message
news:1139343553.343130.288690@.g43g2000cwa.googlegroups.com...
> We have a table that is showing a large amount of "reserved" space:
> Rows: 4095513
> Reserved 11255328 KB
> Data: 1176296 KB
> Index_size: 531240 KB
> unused: 9547792 KB
> (found wiht sp_spaceused)
> We have only simple types in this table... no ntext or blobs or
> anything.
> Just int, smalldatetime, varchar(50) etc. (only 10 fields)
> So our data and indices come to about 1.6 GB, but "unused" space is 9.1
> GB.
> We are running out of drive space...why would it reserve so much space
> for this table?
>
What did you specify when you created the database? Take a look at DBCC
SHRINKFILE.
Rick Sawtell
MCT, MCSD, MCDBA|||Rick,
The DB was created like 10 years ago, so I have no idea what happened
back then.
The DB is set to auto grow by 10%. From what I have read shrinking the
DB won't solve this problem. The DB is 15 GB with just about all of it
being considered "used" (I could get back a couple hundred MB by
shrinking the DB), but the 9GB of space being eaten up by this one
table is what is really painful.
I tried running DBCC CleanTable but that didn't help either.
I'm going to try to insert all the data into a new table and then drop
the old one, but that isn't really ideal.
If there are any other things I can try I would love to give it a go.|||Can you try rebuilding the clustered index? That will automatically move all
the data to new space.
--
HTH
Kalen Delaney, SQL Server MVP
www.solidqualitylearning.com
"cmay" <cmay@.walshgroup.com> wrote in message
news:1139354564.333651.258690@.g14g2000cwa.googlegroups.com...
> Rick,
> The DB was created like 10 years ago, so I have no idea what happened
> back then.
> The DB is set to auto grow by 10%. From what I have read shrinking the
> DB won't solve this problem. The DB is 15 GB with just about all of it
> being considered "used" (I could get back a couple hundred MB by
> shrinking the DB), but the 9GB of space being eaten up by this one
> table is what is really painful.
> I tried running DBCC CleanTable but that didn't help either.
> I'm going to try to insert all the data into a new table and then drop
> the old one, but that isn't really ideal.
> If there are any other things I can try I would love to give it a go.
>|||We actually didn't have a clustered index on this table.
I ended up running an insert from the offending table to a new table,
then dropped the old one, and the new one looks great.|||In general all tables should have a clustered index. You have no way to
control fragmentation or issues like this without one.
--
Andrew J. Kelly SQL MVP
"cmay" <cmay@.walshgroup.com> wrote in message
news:1140532518.546041.33250@.z14g2000cwz.googlegroups.com...
> We actually didn't have a clustered index on this table.
> I ended up running an insert from the offending table to a new table,
> then dropped the old one, and the new one looks great.
>
Friday, March 30, 2012
Recipient name becomes <unknown sender>
Our SQL Server was moved to a new domain. A stored procedure that emails ou
t
with sender's address as [@.v_from = 'abc@.abc.com'] suddenly appears in
Outlook w/o the sender name in "From" column like it used to. In its place
now is <unknown sender>.
Please help.
Gracias
LaEsmeraldaLaEsmeralda wrote:
> Our SQL Server was moved to a new domain. A stored procedure that emails
out
> with sender's address as [@.v_from = 'abc@.abc.com'] suddenly appears in
> Outlook w/o the sender name in "From" column like it used to. In its pla
ce
> now is <unknown sender>.
> Please help.
> Gracias
> LaEsmeralda
What name would you usually see in the from field? It sounds like it's
more of an Outlook problem than it's a SQL server problem. When you send
out emails from Outlook, it will use your Exchange server to resolve the
name into what ever name is in the Global Addresse Book. SInce you've
moved your SQL server to a new domain, it could be that Outlook isn't
able to resolve the name. What happens if you open Outlook on the SQL
server (with the profile that are used for sending out emails) and then
send an email from there. Will you then get the correct name in the
"from" field?
Regards
Steen|||Outlook works normally.
"Steen Persson (DK)" wrote:
> LaEsmeralda wrote:
> What name would you usually see in the from field? It sounds like it's
> more of an Outlook problem than it's a SQL server problem. When you send
> out emails from Outlook, it will use your Exchange server to resolve the
> name into what ever name is in the Global Addresse Book. SInce you've
> moved your SQL server to a new domain, it could be that Outlook isn't
> able to resolve the name. What happens if you open Outlook on the SQL
> server (with the profile that are used for sending out emails) and then
> send an email from there. Will you then get the correct name in the
> "from" field?
> Regards
> Steen
>
t
with sender's address as [@.v_from = 'abc@.abc.com'] suddenly appears in
Outlook w/o the sender name in "From" column like it used to. In its place
now is <unknown sender>.
Please help.
Gracias
LaEsmeraldaLaEsmeralda wrote:
> Our SQL Server was moved to a new domain. A stored procedure that emails
out
> with sender's address as [@.v_from = 'abc@.abc.com'] suddenly appears in
> Outlook w/o the sender name in "From" column like it used to. In its pla
ce
> now is <unknown sender>.
> Please help.
> Gracias
> LaEsmeralda
What name would you usually see in the from field? It sounds like it's
more of an Outlook problem than it's a SQL server problem. When you send
out emails from Outlook, it will use your Exchange server to resolve the
name into what ever name is in the Global Addresse Book. SInce you've
moved your SQL server to a new domain, it could be that Outlook isn't
able to resolve the name. What happens if you open Outlook on the SQL
server (with the profile that are used for sending out emails) and then
send an email from there. Will you then get the correct name in the
"from" field?
Regards
Steen|||Outlook works normally.
"Steen Persson (DK)" wrote:
> LaEsmeralda wrote:
> What name would you usually see in the from field? It sounds like it's
> more of an Outlook problem than it's a SQL server problem. When you send
> out emails from Outlook, it will use your Exchange server to resolve the
> name into what ever name is in the Global Addresse Book. SInce you've
> moved your SQL server to a new domain, it could be that Outlook isn't
> able to resolve the name. What happens if you open Outlook on the SQL
> server (with the profile that are used for sending out emails) and then
> send an email from there. Will you then get the correct name in the
> "from" field?
> Regards
> Steen
>
Recipient name becomes <unknown sender>
Our SQL Server was moved to a new domain. A stored procedure that emails out
with sender's address as [@.v_from = 'abc@.abc.com'] suddenly appears in
Outlook w/o the sender name in "From" column like it used to. In its place
now is <unknown sender>.
Please help.
Gracias
LaEsmeraldaLaEsmeralda wrote:
> Our SQL Server was moved to a new domain. A stored procedure that emails out
> with sender's address as [@.v_from = 'abc@.abc.com'] suddenly appears in
> Outlook w/o the sender name in "From" column like it used to. In its place
> now is <unknown sender>.
> Please help.
> Gracias
> LaEsmeralda
What name would you usually see in the from field? It sounds like it's
more of an Outlook problem than it's a SQL server problem. When you send
out emails from Outlook, it will use your Exchange server to resolve the
name into what ever name is in the Global Addresse Book. SInce you've
moved your SQL server to a new domain, it could be that Outlook isn't
able to resolve the name. What happens if you open Outlook on the SQL
server (with the profile that are used for sending out emails) and then
send an email from there. Will you then get the correct name in the
"from" field?
Regards
Steen|||Outlook works normally.
"Steen Persson (DK)" wrote:
> LaEsmeralda wrote:
> > Our SQL Server was moved to a new domain. A stored procedure that emails out
> > with sender's address as [@.v_from = 'abc@.abc.com'] suddenly appears in
> > Outlook w/o the sender name in "From" column like it used to. In its place
> > now is <unknown sender>.
> > Please help.
> > Gracias
> > LaEsmeralda
> What name would you usually see in the from field? It sounds like it's
> more of an Outlook problem than it's a SQL server problem. When you send
> out emails from Outlook, it will use your Exchange server to resolve the
> name into what ever name is in the Global Addresse Book. SInce you've
> moved your SQL server to a new domain, it could be that Outlook isn't
> able to resolve the name. What happens if you open Outlook on the SQL
> server (with the profile that are used for sending out emails) and then
> send an email from there. Will you then get the correct name in the
> "from" field?
> Regards
> Steen
>
with sender's address as [@.v_from = 'abc@.abc.com'] suddenly appears in
Outlook w/o the sender name in "From" column like it used to. In its place
now is <unknown sender>.
Please help.
Gracias
LaEsmeraldaLaEsmeralda wrote:
> Our SQL Server was moved to a new domain. A stored procedure that emails out
> with sender's address as [@.v_from = 'abc@.abc.com'] suddenly appears in
> Outlook w/o the sender name in "From" column like it used to. In its place
> now is <unknown sender>.
> Please help.
> Gracias
> LaEsmeralda
What name would you usually see in the from field? It sounds like it's
more of an Outlook problem than it's a SQL server problem. When you send
out emails from Outlook, it will use your Exchange server to resolve the
name into what ever name is in the Global Addresse Book. SInce you've
moved your SQL server to a new domain, it could be that Outlook isn't
able to resolve the name. What happens if you open Outlook on the SQL
server (with the profile that are used for sending out emails) and then
send an email from there. Will you then get the correct name in the
"from" field?
Regards
Steen|||Outlook works normally.
"Steen Persson (DK)" wrote:
> LaEsmeralda wrote:
> > Our SQL Server was moved to a new domain. A stored procedure that emails out
> > with sender's address as [@.v_from = 'abc@.abc.com'] suddenly appears in
> > Outlook w/o the sender name in "From" column like it used to. In its place
> > now is <unknown sender>.
> > Please help.
> > Gracias
> > LaEsmeralda
> What name would you usually see in the from field? It sounds like it's
> more of an Outlook problem than it's a SQL server problem. When you send
> out emails from Outlook, it will use your Exchange server to resolve the
> name into what ever name is in the Global Addresse Book. SInce you've
> moved your SQL server to a new domain, it could be that Outlook isn't
> able to resolve the name. What happens if you open Outlook on the SQL
> server (with the profile that are used for sending out emails) and then
> send an email from there. Will you then get the correct name in the
> "from" field?
> Regards
> Steen
>
Recipe for a good, solid maintenance plan
Hello
I'm in the proces of a major revision of the maintenance plans for the SQL servers in our company, and in connection with that I would like to hear how other people are doing this.
Here's a quick rundown of the plan:
Critical DBs will be backed up on tape (daily incremental, weekly full, w. Veritas Backup Exec 9.0). Also, there will be full daily disk backups for easy quick recovery. These will be done locally, as I have bad experiences trying to backup across a network share.
DBs of medium importance will be backed up fully every day on disk. These BAK-files will then be backed up on tape, if I find it necessary.
Although I rarely restore from the tapes, I think they're nice to have in case the office burns down or who knows what.
The maintenance plans will be split into 3:
1. System DBs maint. plan
2. Critical importance DBs maint. plan
3. Medium importance DBs maint. plan
The more I think about it, the more I think I might just classify all production DBs as critical and all test DBs as medium. Maybe that would make more sense.
For all disk backups, optimization and integrity checks (and backup) will be done daily. For DBs of critical importance (eg. production DBs) Transaction log back will be done as well. What's a good schedule for this? Once every 3 hours or so? Every hour? How much burden does this operation put on the server?
I guess that's about it so far. If anyone has any suggestions or comments, I would be very pleased to hear them.
MNJFrequency of trx. log backups depends on the level of activity of action queries and recoverability requirements. In one of our databases here we're doing 15-minute trx. log dumps and the resulting file varies from 800MB to 2.5GB in size. Another database barely creates a 100K logs but we're doing dumps every 30 minutes for its point-in-time recoverability requirements. It all depends.
As per your breakdown, it looks good. But as our disaster recovery excersises shown, - it's beneficial to have your system databases backed up last. Here we're using SQLMAINT utility to run our maintenance plans (SQLMAINT -PlanName <app_db_maint_plan>). This way it's easier to sequence the steps to your likes. Also, do make sure you log all outputs, in case something goes south :)|||[i]As per your breakdown, it looks good. But as our disaster recovery excersises shown, - it's beneficial to have your system databases backed up last. Here we're using SQLMAINT utility to run our maintenance plans (SQLMAINT -PlanName <app_db_maint_plan>). This way it's easier to sequence the steps to your likes. Also, do make sure you log all outputs, in case something goes south :)
Why is it beneficial to backup the system DBs last? Since I keep system and user DBs separated into different maint. plans, I guess I can just schedule the system maint. plan to occur 15 min. after the user main. plan?
MNJ|||For one, if MSDB is backed up last, - it will contain the latest backup information of all other databases, as well as itself. This information is available when looking at the General tab of database Properties window.
As per scheduling, - as I said earlier, I have execution of all maintenance plans in one batch with SQLMAINT. If you're using Scheduled Tasks, then you can add a step with SQLMAINT -PlanName <sys_db_maint_plan> after your application databases.|||Good point with system DBs, I will take that into consideration. I suppose if I just make sure to schedule them a bit apart, it should work out ok.
MNJ
I'm in the proces of a major revision of the maintenance plans for the SQL servers in our company, and in connection with that I would like to hear how other people are doing this.
Here's a quick rundown of the plan:
Critical DBs will be backed up on tape (daily incremental, weekly full, w. Veritas Backup Exec 9.0). Also, there will be full daily disk backups for easy quick recovery. These will be done locally, as I have bad experiences trying to backup across a network share.
DBs of medium importance will be backed up fully every day on disk. These BAK-files will then be backed up on tape, if I find it necessary.
Although I rarely restore from the tapes, I think they're nice to have in case the office burns down or who knows what.
The maintenance plans will be split into 3:
1. System DBs maint. plan
2. Critical importance DBs maint. plan
3. Medium importance DBs maint. plan
The more I think about it, the more I think I might just classify all production DBs as critical and all test DBs as medium. Maybe that would make more sense.
For all disk backups, optimization and integrity checks (and backup) will be done daily. For DBs of critical importance (eg. production DBs) Transaction log back will be done as well. What's a good schedule for this? Once every 3 hours or so? Every hour? How much burden does this operation put on the server?
I guess that's about it so far. If anyone has any suggestions or comments, I would be very pleased to hear them.
MNJFrequency of trx. log backups depends on the level of activity of action queries and recoverability requirements. In one of our databases here we're doing 15-minute trx. log dumps and the resulting file varies from 800MB to 2.5GB in size. Another database barely creates a 100K logs but we're doing dumps every 30 minutes for its point-in-time recoverability requirements. It all depends.
As per your breakdown, it looks good. But as our disaster recovery excersises shown, - it's beneficial to have your system databases backed up last. Here we're using SQLMAINT utility to run our maintenance plans (SQLMAINT -PlanName <app_db_maint_plan>). This way it's easier to sequence the steps to your likes. Also, do make sure you log all outputs, in case something goes south :)|||[i]As per your breakdown, it looks good. But as our disaster recovery excersises shown, - it's beneficial to have your system databases backed up last. Here we're using SQLMAINT utility to run our maintenance plans (SQLMAINT -PlanName <app_db_maint_plan>). This way it's easier to sequence the steps to your likes. Also, do make sure you log all outputs, in case something goes south :)
Why is it beneficial to backup the system DBs last? Since I keep system and user DBs separated into different maint. plans, I guess I can just schedule the system maint. plan to occur 15 min. after the user main. plan?
MNJ|||For one, if MSDB is backed up last, - it will contain the latest backup information of all other databases, as well as itself. This information is available when looking at the General tab of database Properties window.
As per scheduling, - as I said earlier, I have execution of all maintenance plans in one batch with SQLMAINT. If you're using Scheduled Tasks, then you can add a step with SQLMAINT -PlanName <sys_db_maint_plan> after your application databases.|||Good point with system DBs, I will take that into consideration. I suppose if I just make sure to schedule them a bit apart, it should work out ok.
MNJ
Recieving E-Mail by Service broker
I'm beginner...
I need recieve e-mail by Service broker.
What can I do it?
(example if possible).
Thanks!
Service Broker provides reliable messaging in and between databases and does not interface with other systems directly (such as e-mail). You could, however, write a Service Broker service that receives e-mail from IMAP, POP3 or any other e-mail protocol and send them to another Service Broker service. Use Books Online to get started on how to use the technology.
Rushi
|||Thanks!
In some book I read about this.
Probably it isn't true.
|||i'm with you it's true but faile to make it if you found any solve tell me pleaserecieve error in vdi.log when backup SQL 2000 Server DB
using arcserve 2000 to backup database receive error in
VDI.log:
2006/10/05 02:03:24 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at TriggerAbort: invoked
2006/10/05 02:03:43 pid(1312) tid(1892)
Error on DBASQL70TID500VD0
Error at SVDS::Open: Dup(stateEvent) Status Code: 6, x6
Explanation: The handle is invalid.
2006/10/05 02:03:45 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at TriggerAbort: invoked
2006/10/05 02:03:46 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at TriggerAbort: StateEvent Status Code: 6, x6
Explanation: The handle is invalid.
2006/10/05 02:03:46 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at TriggerAbort: CompletionSem Status Code: 6, x6
Explanation: The handle is invalid.
2006/10/05 02:03:46 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at CVDS::Cleanup: Close(State) Status Code: 6, x6
Explanation: The handle is invalid.
2006/10/05 02:03:47 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at CVDS::Cleanup: Close(CompleteSem) Status Code: 6, x6
Explanation: The handle is invalid.
MS SQL Server version is 2000.
Pls help. Thanks
Don't have an answer but check out similar post @. http://forums.databasejournal.com/showthread.php?t=40177sql
VDI.log:
2006/10/05 02:03:24 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at TriggerAbort: invoked
2006/10/05 02:03:43 pid(1312) tid(1892)
Error on DBASQL70TID500VD0
Error at SVDS::Open: Dup(stateEvent) Status Code: 6, x6
Explanation: The handle is invalid.
2006/10/05 02:03:45 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at TriggerAbort: invoked
2006/10/05 02:03:46 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at TriggerAbort: StateEvent Status Code: 6, x6
Explanation: The handle is invalid.
2006/10/05 02:03:46 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at TriggerAbort: CompletionSem Status Code: 6, x6
Explanation: The handle is invalid.
2006/10/05 02:03:46 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at CVDS::Cleanup: Close(State) Status Code: 6, x6
Explanation: The handle is invalid.
2006/10/05 02:03:47 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at CVDS::Cleanup: Close(CompleteSem) Status Code: 6, x6
Explanation: The handle is invalid.
MS SQL Server version is 2000.
Pls help. Thanks
Don't have an answer but check out similar post @. http://forums.databasejournal.com/showthread.php?t=40177sql
Receving error with no description
I have designed quite a few reports over the past few weeks, and today I received the following error:
An error occured during local report processing.
The definition of the report /Discharge7.rdl is invalid.
Exception of type: 'Microsoft.ReportingServices.ReportProcessing.ReportProcessingException' was thrown.
I've never seen this error before. I've gotten errors with typos in names of fields in my expressions, but I've never gotten an error on the 40 someodd other forms I have.
Does anyone know what could be causing this?
Did u tried to preview this report before uploading it to the server, the error says that is not definned correctly, so the report must be bad, when you make a preview on the reporting services it will show you the detailed errors.
|||You can also look at the logs for more detailed error messages. These are located here on a default installation: C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\LogFiles\For more information about the various Reporting Services log files:
http://msdn2.microsoft.com/en-us/library/ms157403.aspx|||This was while I was previewing it in Visual Studio in the report designer. I haven't published it to the server yet.
Recently Rebuilt SQL2K Cluster
I have recently had to rebuild my SQL Server 2000 sp3a 2 node active/passive
cluster running on Windows 2000 AS SP4. We ran into issues about two weeks
ago after a SAN migration (I'll spare all the gory details). When my
previous cluster died, I used one of the nodes as a stand alone instance of
SQL Server (to run our production database). On the other former node, I
removed the OS clustering software and had to manually remove SQL Server. I
eventually (with the assistance of Donna L. at MS) was able to get a single
node cluster of SQL2K running on physical server PRODSQL01 (the virtual
server name is PRODSQLCL01). While the cluster was running as a single node
cluster, I applied sp3a and the 818 hotfix. I then migrated the data from
the stand alone instance to PRODSQLCL01 and started to use it for production.
I turned my attention to the other box and removed and reinstalled the
Windows 2000 cluster software. This box is now called PRODSQL02. I was able
to add PRODSQL02 to the windows cluster, and the successfully added it via
SQL Server setup to the virtual server. My issue now is that PRODSQL02 has
the RTM versions of the binaries. I am not sure if I have a setup issue or I
misunderstand point 3.10 of the sp3a readme. Currently the virtual server is
running on PRODSQL01. If I attempt follow the steps under "If you need to
rebuild a node in the failover cluster..." from PRODSQL02 I am only able to
select the Virtual Server, and if I continue setup I get this error "all
cluster disks available to this virtual server are owned by other node(s)"
and then "Setup was unable to verify the state of the server for an upgrade.
Verify the server is able to start and that you provided a valid sa password
and restart setup". I understand that the virtual resources are only
available on the currently active node, but the way I read the instructions I
should be able to run the service pack installation on the inactive node. Do
I need to rerun the SP (and hotfix) setup on SQL01 (since the virtual server
is running there)? Do I need to move the resources to SQL02 and run the SP
setup there? I just need clarification of where to run the SP setup since I
just added SQL02 to this cluster.
You should be able to run setup on the non-host node and it will upgrade the
local binaries. Try rebooting the newly added RTM node and see if it helps.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
"Justin Hoffmann" <Justin Hoffmann@.discussions.microsoft.com> wrote in
message news:A214ED19-F6CD-4D25-90CE-0A1D456750BD@.microsoft.com...
>I have recently had to rebuild my SQL Server 2000 sp3a 2 node
>active/passive
> cluster running on Windows 2000 AS SP4. We ran into issues about two
> weeks
> ago after a SAN migration (I'll spare all the gory details). When my
> previous cluster died, I used one of the nodes as a stand alone instance
> of
> SQL Server (to run our production database). On the other former node, I
> removed the OS clustering software and had to manually remove SQL Server.
> I
> eventually (with the assistance of Donna L. at MS) was able to get a
> single
> node cluster of SQL2K running on physical server PRODSQL01 (the virtual
> server name is PRODSQLCL01). While the cluster was running as a single
> node
> cluster, I applied sp3a and the 818 hotfix. I then migrated the data from
> the stand alone instance to PRODSQLCL01 and started to use it for
> production.
> I turned my attention to the other box and removed and reinstalled the
> Windows 2000 cluster software. This box is now called PRODSQL02. I was
> able
> to add PRODSQL02 to the windows cluster, and the successfully added it via
> SQL Server setup to the virtual server. My issue now is that PRODSQL02
> has
> the RTM versions of the binaries. I am not sure if I have a setup issue
> or I
> misunderstand point 3.10 of the sp3a readme. Currently the virtual server
> is
> running on PRODSQL01. If I attempt follow the steps under "If you need to
> rebuild a node in the failover cluster..." from PRODSQL02 I am only able
> to
> select the Virtual Server, and if I continue setup I get this error "all
> cluster disks available to this virtual server are owned by other node(s)"
> and then "Setup was unable to verify the state of the server for an
> upgrade.
> Verify the server is able to start and that you provided a valid sa
> password
> and restart setup". I understand that the virtual resources are only
> available on the currently active node, but the way I read the
> instructions I
> should be able to run the service pack installation on the inactive node.
> Do
> I need to rerun the SP (and hotfix) setup on SQL01 (since the virtual
> server
> is running there)? Do I need to move the resources to SQL02 and run the
> SP
> setup there? I just need clarification of where to run the SP setup since
> I
> just added SQL02 to this cluster.
>
|||Geoff:
I've rebooted the newly added RTM node several times and it doesn't seem to
help. When I launch SP3 setup (via setup.bat in the local sql2ksp3
directory) on the newly added RTM node I get to the screen that says Computer
Name. Local Computer is grayed out, there is a box for the existing Virtual
Server name. When I type the virtual server name in the box and press next,
I get the error messages I mentioned in my original post. Is there anything
else you can recommend?
Thanks,
Justin
"Geoff N. Hiten" wrote:
> You should be able to run setup on the non-host node and it will upgrade the
> local binaries. Try rebooting the newly added RTM node and see if it helps.
>
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
>
|||This is how I wound up fixing this:
I ran sp3a setup from PRODSQL01, which was the machine in control of the SQL
Virtual server at the time. It updated the binaries on PRODSQL02, but in
order to do so, the SQL Server service was stopped. Once sp3a setup
completed, I had to reboot PRODSQL02. When it was back up, I verified the
version of the sqlservr.exe file, and it was 8.00.760 (right click,
properties, version). Once I established that sp3a took on the newly added
node, I started the setup for the 8.00.818 security hotfix. SQL Server went
down briefly again, and then the binaries on the newly added box were
updated. I then installed MDAC 2.8 on this node and rebooted. Once
PRODSQL02 was running again I tested moving the cluster resources from 01 to
02. It succeeded. While SQL was running on 02 I ran throught setting up
Imceda SQL Lite Speed (again, it was on 01 but not 02). Once that completed,
I was able to verify that my normally scheduled transaction log backups
completed successfully. Both machines run SQL Server and perform the
backups correctly. I am not sure about the root cause of the issue I
encountered with not being able to run the sp and hotfix on the newly added
node when it wasn't running the Virtual SQL Server (the sp3a readme seems to
indicate that you can), but I finally have a 2 node active passive cluster
running again.
|||Just to clarify, it is active passive, so only one node runs the Virtual SQL
Server at any time. I was trying to say that each node is able to run SQL
Server, and each node is able to run the SQL Lite Speed backups. I had been
concerned that somehow I would get PRODSQL02 all patched but then failing
over would not work correctly. Everything is working OK.
"Justin Hoffmann" wrote:
> This is how I wound up fixing this:
> I ran sp3a setup from PRODSQL01, which was the machine in control of the SQL
> Virtual server at the time. It updated the binaries on PRODSQL02, but in
> order to do so, the SQL Server service was stopped. Once sp3a setup
> completed, I had to reboot PRODSQL02. When it was back up, I verified the
> version of the sqlservr.exe file, and it was 8.00.760 (right click,
> properties, version). Once I established that sp3a took on the newly added
> node, I started the setup for the 8.00.818 security hotfix. SQL Server went
> down briefly again, and then the binaries on the newly added box were
> updated. I then installed MDAC 2.8 on this node and rebooted. Once
> PRODSQL02 was running again I tested moving the cluster resources from 01 to
> 02. It succeeded. While SQL was running on 02 I ran throught setting up
> Imceda SQL Lite Speed (again, it was on 01 but not 02). Once that completed,
> I was able to verify that my normally scheduled transaction log backups
> completed successfully. Both machines run SQL Server and perform the
> backups correctly. I am not sure about the root cause of the issue I
> encountered with not being able to run the sp and hotfix on the newly added
> node when it wasn't running the Virtual SQL Server (the sp3a readme seems to
> indicate that you can), but I finally have a 2 node active passive cluster
> running again.
|||The current correct term is "Single-Instance". "Active-Active" and its
cousins all refer to technology used specifically in SQL server 7.0 only.
Sometimes the binary only upgrade doesn't work right. Your solution is the
fallback solution but it does have the obvious downside of taking the SQL
server offline for a short time during the upgrade.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Adminstrator
"Justin Hoffmann" <JustinHoffmann@.discussions.microsoft.com> wrote in
message news:DA3E156A-EAFD-45D9-B72E-AB4A657D53A0@.microsoft.com...[vbcol=seagreen]
> Just to clarify, it is active passive, so only one node runs the Virtual
> SQL
> Server at any time. I was trying to say that each node is able to run SQL
> Server, and each node is able to run the SQL Lite Speed backups. I had
> been
> concerned that somehow I would get PRODSQL02 all patched but then failing
> over would not work correctly. Everything is working OK.
> "Justin Hoffmann" wrote:
cluster running on Windows 2000 AS SP4. We ran into issues about two weeks
ago after a SAN migration (I'll spare all the gory details). When my
previous cluster died, I used one of the nodes as a stand alone instance of
SQL Server (to run our production database). On the other former node, I
removed the OS clustering software and had to manually remove SQL Server. I
eventually (with the assistance of Donna L. at MS) was able to get a single
node cluster of SQL2K running on physical server PRODSQL01 (the virtual
server name is PRODSQLCL01). While the cluster was running as a single node
cluster, I applied sp3a and the 818 hotfix. I then migrated the data from
the stand alone instance to PRODSQLCL01 and started to use it for production.
I turned my attention to the other box and removed and reinstalled the
Windows 2000 cluster software. This box is now called PRODSQL02. I was able
to add PRODSQL02 to the windows cluster, and the successfully added it via
SQL Server setup to the virtual server. My issue now is that PRODSQL02 has
the RTM versions of the binaries. I am not sure if I have a setup issue or I
misunderstand point 3.10 of the sp3a readme. Currently the virtual server is
running on PRODSQL01. If I attempt follow the steps under "If you need to
rebuild a node in the failover cluster..." from PRODSQL02 I am only able to
select the Virtual Server, and if I continue setup I get this error "all
cluster disks available to this virtual server are owned by other node(s)"
and then "Setup was unable to verify the state of the server for an upgrade.
Verify the server is able to start and that you provided a valid sa password
and restart setup". I understand that the virtual resources are only
available on the currently active node, but the way I read the instructions I
should be able to run the service pack installation on the inactive node. Do
I need to rerun the SP (and hotfix) setup on SQL01 (since the virtual server
is running there)? Do I need to move the resources to SQL02 and run the SP
setup there? I just need clarification of where to run the SP setup since I
just added SQL02 to this cluster.
You should be able to run setup on the non-host node and it will upgrade the
local binaries. Try rebooting the newly added RTM node and see if it helps.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
"Justin Hoffmann" <Justin Hoffmann@.discussions.microsoft.com> wrote in
message news:A214ED19-F6CD-4D25-90CE-0A1D456750BD@.microsoft.com...
>I have recently had to rebuild my SQL Server 2000 sp3a 2 node
>active/passive
> cluster running on Windows 2000 AS SP4. We ran into issues about two
> weeks
> ago after a SAN migration (I'll spare all the gory details). When my
> previous cluster died, I used one of the nodes as a stand alone instance
> of
> SQL Server (to run our production database). On the other former node, I
> removed the OS clustering software and had to manually remove SQL Server.
> I
> eventually (with the assistance of Donna L. at MS) was able to get a
> single
> node cluster of SQL2K running on physical server PRODSQL01 (the virtual
> server name is PRODSQLCL01). While the cluster was running as a single
> node
> cluster, I applied sp3a and the 818 hotfix. I then migrated the data from
> the stand alone instance to PRODSQLCL01 and started to use it for
> production.
> I turned my attention to the other box and removed and reinstalled the
> Windows 2000 cluster software. This box is now called PRODSQL02. I was
> able
> to add PRODSQL02 to the windows cluster, and the successfully added it via
> SQL Server setup to the virtual server. My issue now is that PRODSQL02
> has
> the RTM versions of the binaries. I am not sure if I have a setup issue
> or I
> misunderstand point 3.10 of the sp3a readme. Currently the virtual server
> is
> running on PRODSQL01. If I attempt follow the steps under "If you need to
> rebuild a node in the failover cluster..." from PRODSQL02 I am only able
> to
> select the Virtual Server, and if I continue setup I get this error "all
> cluster disks available to this virtual server are owned by other node(s)"
> and then "Setup was unable to verify the state of the server for an
> upgrade.
> Verify the server is able to start and that you provided a valid sa
> password
> and restart setup". I understand that the virtual resources are only
> available on the currently active node, but the way I read the
> instructions I
> should be able to run the service pack installation on the inactive node.
> Do
> I need to rerun the SP (and hotfix) setup on SQL01 (since the virtual
> server
> is running there)? Do I need to move the resources to SQL02 and run the
> SP
> setup there? I just need clarification of where to run the SP setup since
> I
> just added SQL02 to this cluster.
>
|||Geoff:
I've rebooted the newly added RTM node several times and it doesn't seem to
help. When I launch SP3 setup (via setup.bat in the local sql2ksp3
directory) on the newly added RTM node I get to the screen that says Computer
Name. Local Computer is grayed out, there is a box for the existing Virtual
Server name. When I type the virtual server name in the box and press next,
I get the error messages I mentioned in my original post. Is there anything
else you can recommend?
Thanks,
Justin
"Geoff N. Hiten" wrote:
> You should be able to run setup on the non-host node and it will upgrade the
> local binaries. Try rebooting the newly added RTM node and see if it helps.
>
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
>
|||This is how I wound up fixing this:
I ran sp3a setup from PRODSQL01, which was the machine in control of the SQL
Virtual server at the time. It updated the binaries on PRODSQL02, but in
order to do so, the SQL Server service was stopped. Once sp3a setup
completed, I had to reboot PRODSQL02. When it was back up, I verified the
version of the sqlservr.exe file, and it was 8.00.760 (right click,
properties, version). Once I established that sp3a took on the newly added
node, I started the setup for the 8.00.818 security hotfix. SQL Server went
down briefly again, and then the binaries on the newly added box were
updated. I then installed MDAC 2.8 on this node and rebooted. Once
PRODSQL02 was running again I tested moving the cluster resources from 01 to
02. It succeeded. While SQL was running on 02 I ran throught setting up
Imceda SQL Lite Speed (again, it was on 01 but not 02). Once that completed,
I was able to verify that my normally scheduled transaction log backups
completed successfully. Both machines run SQL Server and perform the
backups correctly. I am not sure about the root cause of the issue I
encountered with not being able to run the sp and hotfix on the newly added
node when it wasn't running the Virtual SQL Server (the sp3a readme seems to
indicate that you can), but I finally have a 2 node active passive cluster
running again.
|||Just to clarify, it is active passive, so only one node runs the Virtual SQL
Server at any time. I was trying to say that each node is able to run SQL
Server, and each node is able to run the SQL Lite Speed backups. I had been
concerned that somehow I would get PRODSQL02 all patched but then failing
over would not work correctly. Everything is working OK.
"Justin Hoffmann" wrote:
> This is how I wound up fixing this:
> I ran sp3a setup from PRODSQL01, which was the machine in control of the SQL
> Virtual server at the time. It updated the binaries on PRODSQL02, but in
> order to do so, the SQL Server service was stopped. Once sp3a setup
> completed, I had to reboot PRODSQL02. When it was back up, I verified the
> version of the sqlservr.exe file, and it was 8.00.760 (right click,
> properties, version). Once I established that sp3a took on the newly added
> node, I started the setup for the 8.00.818 security hotfix. SQL Server went
> down briefly again, and then the binaries on the newly added box were
> updated. I then installed MDAC 2.8 on this node and rebooted. Once
> PRODSQL02 was running again I tested moving the cluster resources from 01 to
> 02. It succeeded. While SQL was running on 02 I ran throught setting up
> Imceda SQL Lite Speed (again, it was on 01 but not 02). Once that completed,
> I was able to verify that my normally scheduled transaction log backups
> completed successfully. Both machines run SQL Server and perform the
> backups correctly. I am not sure about the root cause of the issue I
> encountered with not being able to run the sp and hotfix on the newly added
> node when it wasn't running the Virtual SQL Server (the sp3a readme seems to
> indicate that you can), but I finally have a 2 node active passive cluster
> running again.
|||The current correct term is "Single-Instance". "Active-Active" and its
cousins all refer to technology used specifically in SQL server 7.0 only.
Sometimes the binary only upgrade doesn't work right. Your solution is the
fallback solution but it does have the obvious downside of taking the SQL
server offline for a short time during the upgrade.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Adminstrator
"Justin Hoffmann" <JustinHoffmann@.discussions.microsoft.com> wrote in
message news:DA3E156A-EAFD-45D9-B72E-AB4A657D53A0@.microsoft.com...[vbcol=seagreen]
> Just to clarify, it is active passive, so only one node runs the Virtual
> SQL
> Server at any time. I was trying to say that each node is able to run SQL
> Server, and each node is able to run the SQL Lite Speed backups. I had
> been
> concerned that somehow I would get PRODSQL02 all patched but then failing
> over would not work correctly. Everything is working OK.
> "Justin Hoffmann" wrote:
Recently I lost my job
Hi All,
Recently I lost my job, which I had for 6 years, because someone accused me
that I destroyed critical data on a Microsoft SB2000 server.
The damage was done on the SQL server data, so the commercial application
was malfunctioning.
The guy who wrote the commercial application (ERP) said that has evidence
showing that the damage was done from me. My poor knowledge of MS SB2000 and
SQL server and the thread that if I refuse the category they will get me in
the court, I forced to accept the category and leave the company that I
worked for 6 years.
Now I have a new better job, but I try to fix again my name and my image of
the 25 year professional work in computer industry
In my trial to prove that I am innocent and I have not damage any data I
need any possible help for the following.
If I can get from any log or other kind of tracing
a -not editable - (read only) information, so I can used it as evidence
Any help is welcome
Evan K
You could try to read the transaction log, if it is still available to you.
From there, with an appropriate tool, you can see who did what. Check, for
example, Lumigent Log Explorer (http://www.lumigent.com/).
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Evan Kosterolgou" <EvanKosterolgou@.discussions.microsoft.com> wrote in
message news:2C91534F-A527-4BDE-854D-9076CD7035E7@.microsoft.com...
> Hi All,
> Recently I lost my job, which I had for 6 years, because someone accused
me
> that I destroyed critical data on a Microsoft SB2000 server.
> The damage was done on the SQL server data, so the commercial application
> was malfunctioning.
> The guy who wrote the commercial application (ERP) said that has evidence
> showing that the damage was done from me. My poor knowledge of MS SB2000
and
> SQL server and the thread that if I refuse the category they will get me
in
> the court, I forced to accept the category and leave the company that I
> worked for 6 years.
> Now I have a new better job, but I try to fix again my name and my image
of
> the 25 year professional work in computer industry
> In my trial to prove that I am innocent and I have not damage any data I
> need any possible help for the following.
> If I can get from any log or other kind of tracing
> a -not editable - (read only) information, so I can used it as evidence
> Any help is welcome
> Evan K
|||"Evan Kosterolgou" <EvanKosterolgou@.discussions.microsoft.com> wrote in
message news:2C91534F-A527-4BDE-854D-9076CD7035E7@.microsoft.com...
> Hi All,
> Recently I lost my job, which I had for 6 years, because someone accused
> me
> that I destroyed critical data on a Microsoft SB2000 server.
> The damage was done on the SQL server data, so the commercial application
> was malfunctioning.
> The guy who wrote the commercial application (ERP) said that has evidence
> showing that the damage was done from me. My poor knowledge of MS SB2000
> and
> SQL server and the thread that if I refuse the category they will get me
> in
> the court, I forced to accept the category and leave the company that I
> worked for 6 years.
I'm just surprised on how s/he manage to say that you're the culprit.
Anyway, below are just to share my experiences. Believe me, it was a very
painful and grueling process to identify how the server was hacked.
An external hacker hacked into our system, replace a compiled .dll file by
appending 'drop table x'. To cut a long story short, it was because of too
much rights given to one of the directory in the IIS (which has the compiled
VB stored procedure in .dll) because the so called developer just know how
to program ERP systems, but has very minimal knowledge in managing an IIS
server let alone an application server.
There are (many) software (search for vb decompiler) that is able to read
the compiled .dll and de-compile.
Since the hacker overwrite the DLL file with his/her version, the SQL
profiler shows that the command was issued via a valid connection, ie from
someone in the local Intranet. Meaning, everytime someone logs into the ERP
system, the command "drop table x" would be issued.
This can also be confirmed by installing Ethereal network packet analyzer to
analyze the packets in real time.
We got lucky and we manage to pinpoint some files being changed by the so
called hacker. After that discovery it was just a matter of how to prevent
people from writing to the IIS.
However, I'm not sure if the above can be of any use to you and good luck.
(Sorry for my bad english as it is not my first language)
> Now I have a new better job, but I try to fix again my name and my image
> of
> the 25 year professional work in computer industry
> In my trial to prove that I am innocent and I have not damage any data I
> need any possible help for the following.
> If I can get from any log or other kind of tracing
> a -not editable - (read only) information, so I can used it as evidence
> Any help is welcome
Steven Ung
|||Thanks A LOT
"Dejan Sarka" wrote:
> You could try to read the transaction log, if it is still available to you.
> From there, with an appropriate tool, you can see who did what. Check, for
> example, Lumigent Log Explorer (http://www.lumigent.com/).
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> www.SolidQualityLearning.com
> "Evan Kosterolgou" <EvanKosterolgou@.discussions.microsoft.com> wrote in
> message news:2C91534F-A527-4BDE-854D-9076CD7035E7@.microsoft.com...
> me
> and
> in
> of
>
>
|||Thanks Steven
"Steven Ung" wrote:
> "Evan Kosterolgou" <EvanKosterolgou@.discussions.microsoft.com> wrote in
> message news:2C91534F-A527-4BDE-854D-9076CD7035E7@.microsoft.com...
> I'm just surprised on how s/he manage to say that you're the culprit.
> Anyway, below are just to share my experiences. Believe me, it was a very
> painful and grueling process to identify how the server was hacked.
> An external hacker hacked into our system, replace a compiled .dll file by
> appending 'drop table x'. To cut a long story short, it was because of too
> much rights given to one of the directory in the IIS (which has the compiled
> VB stored procedure in .dll) because the so called developer just know how
> to program ERP systems, but has very minimal knowledge in managing an IIS
> server let alone an application server.
> There are (many) software (search for vb decompiler) that is able to read
> the compiled .dll and de-compile.
> Since the hacker overwrite the DLL file with his/her version, the SQL
> profiler shows that the command was issued via a valid connection, ie from
> someone in the local Intranet. Meaning, everytime someone logs into the ERP
> system, the command "drop table x" would be issued.
> This can also be confirmed by installing Ethereal network packet analyzer to
> analyze the packets in real time.
> We got lucky and we manage to pinpoint some files being changed by the so
> called hacker. After that discovery it was just a matter of how to prevent
> people from writing to the IIS.
> However, I'm not sure if the above can be of any use to you and good luck.
> (Sorry for my bad english as it is not my first language)
>
> --
> Steven Ung
>
>
Recently I lost my job, which I had for 6 years, because someone accused me
that I destroyed critical data on a Microsoft SB2000 server.
The damage was done on the SQL server data, so the commercial application
was malfunctioning.
The guy who wrote the commercial application (ERP) said that has evidence
showing that the damage was done from me. My poor knowledge of MS SB2000 and
SQL server and the thread that if I refuse the category they will get me in
the court, I forced to accept the category and leave the company that I
worked for 6 years.
Now I have a new better job, but I try to fix again my name and my image of
the 25 year professional work in computer industry
In my trial to prove that I am innocent and I have not damage any data I
need any possible help for the following.
If I can get from any log or other kind of tracing
a -not editable - (read only) information, so I can used it as evidence
Any help is welcome
Evan K
You could try to read the transaction log, if it is still available to you.
From there, with an appropriate tool, you can see who did what. Check, for
example, Lumigent Log Explorer (http://www.lumigent.com/).
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
"Evan Kosterolgou" <EvanKosterolgou@.discussions.microsoft.com> wrote in
message news:2C91534F-A527-4BDE-854D-9076CD7035E7@.microsoft.com...
> Hi All,
> Recently I lost my job, which I had for 6 years, because someone accused
me
> that I destroyed critical data on a Microsoft SB2000 server.
> The damage was done on the SQL server data, so the commercial application
> was malfunctioning.
> The guy who wrote the commercial application (ERP) said that has evidence
> showing that the damage was done from me. My poor knowledge of MS SB2000
and
> SQL server and the thread that if I refuse the category they will get me
in
> the court, I forced to accept the category and leave the company that I
> worked for 6 years.
> Now I have a new better job, but I try to fix again my name and my image
of
> the 25 year professional work in computer industry
> In my trial to prove that I am innocent and I have not damage any data I
> need any possible help for the following.
> If I can get from any log or other kind of tracing
> a -not editable - (read only) information, so I can used it as evidence
> Any help is welcome
> Evan K
|||"Evan Kosterolgou" <EvanKosterolgou@.discussions.microsoft.com> wrote in
message news:2C91534F-A527-4BDE-854D-9076CD7035E7@.microsoft.com...
> Hi All,
> Recently I lost my job, which I had for 6 years, because someone accused
> me
> that I destroyed critical data on a Microsoft SB2000 server.
> The damage was done on the SQL server data, so the commercial application
> was malfunctioning.
> The guy who wrote the commercial application (ERP) said that has evidence
> showing that the damage was done from me. My poor knowledge of MS SB2000
> and
> SQL server and the thread that if I refuse the category they will get me
> in
> the court, I forced to accept the category and leave the company that I
> worked for 6 years.
I'm just surprised on how s/he manage to say that you're the culprit.
Anyway, below are just to share my experiences. Believe me, it was a very
painful and grueling process to identify how the server was hacked.
An external hacker hacked into our system, replace a compiled .dll file by
appending 'drop table x'. To cut a long story short, it was because of too
much rights given to one of the directory in the IIS (which has the compiled
VB stored procedure in .dll) because the so called developer just know how
to program ERP systems, but has very minimal knowledge in managing an IIS
server let alone an application server.
There are (many) software (search for vb decompiler) that is able to read
the compiled .dll and de-compile.
Since the hacker overwrite the DLL file with his/her version, the SQL
profiler shows that the command was issued via a valid connection, ie from
someone in the local Intranet. Meaning, everytime someone logs into the ERP
system, the command "drop table x" would be issued.
This can also be confirmed by installing Ethereal network packet analyzer to
analyze the packets in real time.
We got lucky and we manage to pinpoint some files being changed by the so
called hacker. After that discovery it was just a matter of how to prevent
people from writing to the IIS.
However, I'm not sure if the above can be of any use to you and good luck.
(Sorry for my bad english as it is not my first language)
> Now I have a new better job, but I try to fix again my name and my image
> of
> the 25 year professional work in computer industry
> In my trial to prove that I am innocent and I have not damage any data I
> need any possible help for the following.
> If I can get from any log or other kind of tracing
> a -not editable - (read only) information, so I can used it as evidence
> Any help is welcome
Steven Ung
|||Thanks A LOT
"Dejan Sarka" wrote:
> You could try to read the transaction log, if it is still available to you.
> From there, with an appropriate tool, you can see who did what. Check, for
> example, Lumigent Log Explorer (http://www.lumigent.com/).
> --
> Dejan Sarka, SQL Server MVP
> Associate Mentor
> www.SolidQualityLearning.com
> "Evan Kosterolgou" <EvanKosterolgou@.discussions.microsoft.com> wrote in
> message news:2C91534F-A527-4BDE-854D-9076CD7035E7@.microsoft.com...
> me
> and
> in
> of
>
>
|||Thanks Steven
"Steven Ung" wrote:
> "Evan Kosterolgou" <EvanKosterolgou@.discussions.microsoft.com> wrote in
> message news:2C91534F-A527-4BDE-854D-9076CD7035E7@.microsoft.com...
> I'm just surprised on how s/he manage to say that you're the culprit.
> Anyway, below are just to share my experiences. Believe me, it was a very
> painful and grueling process to identify how the server was hacked.
> An external hacker hacked into our system, replace a compiled .dll file by
> appending 'drop table x'. To cut a long story short, it was because of too
> much rights given to one of the directory in the IIS (which has the compiled
> VB stored procedure in .dll) because the so called developer just know how
> to program ERP systems, but has very minimal knowledge in managing an IIS
> server let alone an application server.
> There are (many) software (search for vb decompiler) that is able to read
> the compiled .dll and de-compile.
> Since the hacker overwrite the DLL file with his/her version, the SQL
> profiler shows that the command was issued via a valid connection, ie from
> someone in the local Intranet. Meaning, everytime someone logs into the ERP
> system, the command "drop table x" would be issued.
> This can also be confirmed by installing Ethereal network packet analyzer to
> analyze the packets in real time.
> We got lucky and we manage to pinpoint some files being changed by the so
> called hacker. After that discovery it was just a matter of how to prevent
> people from writing to the IIS.
> However, I'm not sure if the above can be of any use to you and good luck.
> (Sorry for my bad english as it is not my first language)
>
> --
> Steven Ung
>
>
Recent SSRS books?
I will be starting a new project using SS2005 Reporting Services. Can
someone recommend 2 or 3 books on the subject? I am interested in a
book beyond the basics. (I believe I don't need the hand holding, or
"step by step," as that most of that can be found online.)
We will be applying report security and integrating with SharePoint in
the near future as well.
I found these so far.
1) Mastering SQL Server 2005 Reporting Services Infrastructure Design
(Joseph L. Jorden - Sybex, Published 2007)
2) Microsoft SQL Server 2005 Reporting Services (Brian Larson - McGraw-
Hill, Published 2005)
The first book listed above has a section discussing role based
security and SharePoint deployment. Are these mostly a slam dunk and
I don't need this in a book?
Has much changed since 2005? There are many books from 2005/2006 and
a few published more recently.
Thanks in advance!
DanI can recomend :-
http://www.amazon.co.uk/Hitchhikers-Guide-Visual-Studio-Server/dp/0321243625/ref=sr_1_1?ie=UTF8&s=books&qid=1196846573&sr=8-1
It covers most topics and starts at a level where you are expected to have
had a play with reporting services and mastered some of the basics of
creating reports.
Cheers
Dale
"ZCSI" <danzemmels@.gmail.com> wrote in message
news:f07e2e87-d3f8-4cd4-a9db-db259766e31d@.y43g2000hsy.googlegroups.com...
>I will be starting a new project using SS2005 Reporting Services. Can
> someone recommend 2 or 3 books on the subject? I am interested in a
> book beyond the basics. (I believe I don't need the hand holding, or
> "step by step," as that most of that can be found online.)
> We will be applying report security and integrating with SharePoint in
> the near future as well.
> I found these so far.
> 1) Mastering SQL Server 2005 Reporting Services Infrastructure Design
> (Joseph L. Jorden - Sybex, Published 2007)
> 2) Microsoft SQL Server 2005 Reporting Services (Brian Larson - McGraw-
> Hill, Published 2005)
> The first book listed above has a section discussing role based
> security and SharePoint deployment. Are these mostly a slam dunk and
> I don't need this in a book?
> Has much changed since 2005? There are many books from 2005/2006 and
> a few published more recently.
> Thanks in advance!
> Dan|||I have the Brian Larson book on my desk, and it's really helpful, but I'm not
a developper but a DBA. So I'm more interested in the technical en security
side of RS.
But it's a good book, and it does the trick for me.
"Dale" wrote:
> I can recomend :-
> http://www.amazon.co.uk/Hitchhikers-Guide-Visual-Studio-Server/dp/0321243625/ref=sr_1_1?ie=UTF8&s=books&qid=1196846573&sr=8-1
> It covers most topics and starts at a level where you are expected to have
> had a play with reporting services and mastered some of the basics of
> creating reports.
> Cheers
> Dale
>
> "ZCSI" <danzemmels@.gmail.com> wrote in message
> news:f07e2e87-d3f8-4cd4-a9db-db259766e31d@.y43g2000hsy.googlegroups.com...
> >I will be starting a new project using SS2005 Reporting Services. Can
> > someone recommend 2 or 3 books on the subject? I am interested in a
> > book beyond the basics. (I believe I don't need the hand holding, or
> > "step by step," as that most of that can be found online.)
> >
> > We will be applying report security and integrating with SharePoint in
> > the near future as well.
> >
> > I found these so far.
> > 1) Mastering SQL Server 2005 Reporting Services Infrastructure Design
> > (Joseph L. Jorden - Sybex, Published 2007)
> > 2) Microsoft SQL Server 2005 Reporting Services (Brian Larson - McGraw-
> > Hill, Published 2005)
> >
> > The first book listed above has a section discussing role based
> > security and SharePoint deployment. Are these mostly a slam dunk and
> > I don't need this in a book?
> >
> > Has much changed since 2005? There are many books from 2005/2006 and
> > a few published more recently.
> >
> > Thanks in advance!
> > Dan
>
>
someone recommend 2 or 3 books on the subject? I am interested in a
book beyond the basics. (I believe I don't need the hand holding, or
"step by step," as that most of that can be found online.)
We will be applying report security and integrating with SharePoint in
the near future as well.
I found these so far.
1) Mastering SQL Server 2005 Reporting Services Infrastructure Design
(Joseph L. Jorden - Sybex, Published 2007)
2) Microsoft SQL Server 2005 Reporting Services (Brian Larson - McGraw-
Hill, Published 2005)
The first book listed above has a section discussing role based
security and SharePoint deployment. Are these mostly a slam dunk and
I don't need this in a book?
Has much changed since 2005? There are many books from 2005/2006 and
a few published more recently.
Thanks in advance!
DanI can recomend :-
http://www.amazon.co.uk/Hitchhikers-Guide-Visual-Studio-Server/dp/0321243625/ref=sr_1_1?ie=UTF8&s=books&qid=1196846573&sr=8-1
It covers most topics and starts at a level where you are expected to have
had a play with reporting services and mastered some of the basics of
creating reports.
Cheers
Dale
"ZCSI" <danzemmels@.gmail.com> wrote in message
news:f07e2e87-d3f8-4cd4-a9db-db259766e31d@.y43g2000hsy.googlegroups.com...
>I will be starting a new project using SS2005 Reporting Services. Can
> someone recommend 2 or 3 books on the subject? I am interested in a
> book beyond the basics. (I believe I don't need the hand holding, or
> "step by step," as that most of that can be found online.)
> We will be applying report security and integrating with SharePoint in
> the near future as well.
> I found these so far.
> 1) Mastering SQL Server 2005 Reporting Services Infrastructure Design
> (Joseph L. Jorden - Sybex, Published 2007)
> 2) Microsoft SQL Server 2005 Reporting Services (Brian Larson - McGraw-
> Hill, Published 2005)
> The first book listed above has a section discussing role based
> security and SharePoint deployment. Are these mostly a slam dunk and
> I don't need this in a book?
> Has much changed since 2005? There are many books from 2005/2006 and
> a few published more recently.
> Thanks in advance!
> Dan|||I have the Brian Larson book on my desk, and it's really helpful, but I'm not
a developper but a DBA. So I'm more interested in the technical en security
side of RS.
But it's a good book, and it does the trick for me.
"Dale" wrote:
> I can recomend :-
> http://www.amazon.co.uk/Hitchhikers-Guide-Visual-Studio-Server/dp/0321243625/ref=sr_1_1?ie=UTF8&s=books&qid=1196846573&sr=8-1
> It covers most topics and starts at a level where you are expected to have
> had a play with reporting services and mastered some of the basics of
> creating reports.
> Cheers
> Dale
>
> "ZCSI" <danzemmels@.gmail.com> wrote in message
> news:f07e2e87-d3f8-4cd4-a9db-db259766e31d@.y43g2000hsy.googlegroups.com...
> >I will be starting a new project using SS2005 Reporting Services. Can
> > someone recommend 2 or 3 books on the subject? I am interested in a
> > book beyond the basics. (I believe I don't need the hand holding, or
> > "step by step," as that most of that can be found online.)
> >
> > We will be applying report security and integrating with SharePoint in
> > the near future as well.
> >
> > I found these so far.
> > 1) Mastering SQL Server 2005 Reporting Services Infrastructure Design
> > (Joseph L. Jorden - Sybex, Published 2007)
> > 2) Microsoft SQL Server 2005 Reporting Services (Brian Larson - McGraw-
> > Hill, Published 2005)
> >
> > The first book listed above has a section discussing role based
> > security and SharePoint deployment. Are these mostly a slam dunk and
> > I don't need this in a book?
> >
> > Has much changed since 2005? There are many books from 2005/2006 and
> > a few published more recently.
> >
> > Thanks in advance!
> > Dan
>
>
recent SQL 2005 hotfix creates problem
Here are the errors in event log. The installation packeage keeps trying
every 3 hours. How shouyld I fix it.
Microsoft SQL Server 2005 Tools Express Edition -- Install started.
Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
installer has encountered an unexpected error. The error code is 2711. The
specified Feature name ('SQL_Documentation') not found in Feature table.
Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
not be installed. Error code 1603. Additional information is available in the
log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB932557_sql run_tools.msp.log.
Hi
"fj" wrote:
> Here are the errors in event log. The installation packeage keeps trying
> every 3 hours. How shouyld I fix it.
>
> Microsoft SQL Server 2005 Tools Express Edition -- Install started.
> Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
> installer has encountered an unexpected error. The error code is 2711. The
> specified Feature name ('SQL_Documentation') not found in Feature table.
> Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
> for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
> not be installed. Error code 1603. Additional information is available in the
> log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB932557_sql run_tools.msp.log.
What does this log say?
It may be similar to http://support.microsoft.com/kb/916760/en-us
or http://support.microsoft.com/kb/834484/en-us i.e. the permissions or
folders expected may not exist or have the wrong permissions or the account
doing the install may not have enough permissions.
John
|||Here is the part I found that might cause the problem. The specified Feature
name ('SQL_Documentation') not found in Feature table.
....
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E, Object:
C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a 1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget, Object:
C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
Express Edition -- Error 2711. The installer has encountered an unexpected
error. The error code is 2711. The specified Feature name
('SQL_Documentation') not found in Feature table.
Error 2711. The installer has encountered an unexpected error. The error
code is 2711. The specified Feature name ('SQL_Documentation') not found in
Feature table.
Action ended 9:51:03: CostFinalize. Return value 3.
Action ended 9:51:03: INSTALL. Return value 3.
Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Property(S): ProductLanguage = 1033
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.00.1399.06
Property(S): MEDIAPACKAGEPATH = \Setup\
....
|||Hi
"fj" wrote:
> Here is the part I found that might cause the problem. The specified Feature
> name ('SQL_Documentation') not found in Feature table.
>
> ...
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E, Object:
> C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a 1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget, Object:
> C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
> Express Edition -- Error 2711. The installer has encountered an unexpected
> error. The error code is 2711. The specified Feature name
> ('SQL_Documentation') not found in Feature table.
> Error 2711. The installer has encountered an unexpected error. The error
> code is 2711. The specified Feature name ('SQL_Documentation') not found in
> Feature table.
> Action ended 9:51:03: CostFinalize. Return value 3.
> Action ended 9:51:03: INSTALL. Return value 3.
> Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> Property(S): ProductLanguage = 1033
> Property(S): Manufacturer = Microsoft Corporation
> Property(S): ProductVersion = 9.00.1399.06
> Property(S): MEDIAPACKAGEPATH = \Setup\
> ...
SQL Express is not one of the products that have been listed as affected by
the hotfix!
http://support.microsoft.com/kb/932557/en-us
John
|||"John Bell" wrote:
> Hi
> "fj" wrote:
>
> SQL Express is not one of the products that have been listed as affected by
> the hotfix!
> http://support.microsoft.com/kb/932557/en-us
> John
Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
installed by auto-update.
Now it seems like there is a scheduled job at somewhere, how I can stop or
remove it?
Is the hotfix referred by your link a fix to the problem?
Thanks
-FJ
|||Hi
"fj" wrote:
>
> "John Bell" wrote:
>
> Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
> installed by auto-update.
> Now it seems like there is a scheduled job at somewhere, how I can stop or
> remove it?
> Is the hotfix referred by your link a fix to the problem?
> Thanks
> -FJ
It looks like you may have something left over then, if you have removed it.
You may want to check out:
http://msdn2.microsoft.com/en-us/vstudio/aa718704.aspx
or http://support.microsoft.com/kb/909967
John
|||Thanks John,
Actually I found the problem is because I didn't install the client tool and
documents from the original 2005 SQL Server(64bit). BUT, the auto-update
downloaded the hotfix for the SQL server 2005 without checking if I need this
fix. This hotfix (MSDN article number 932557) has "hardwired" update for
those tools and docs whch I don't have so the update failed.
Since the update is scheduled to launch every 3 hours, I am keep getting
this annoying errors.
Now my question still remains, how I can terminate the remaining update
manually? Is there a way to intercept MicroSoft's auto-update?
I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
bug in this hotfix and Microsoft needs to know that.
Thanks
-FJ
|||Hi
"fj" wrote:
> Thanks John,
> Actually I found the problem is because I didn't install the client tool and
> documents from the original 2005 SQL Server(64bit). BUT, the auto-update
> downloaded the hotfix for the SQL server 2005 without checking if I need this
> fix. This hotfix (MSDN article number 932557) has "hardwired" update for
> those tools and docs whch I don't have so the update failed.
> Since the update is scheduled to launch every 3 hours, I am keep getting
> this annoying errors.
> Now my question still remains, how I can terminate the remaining update
> manually? Is there a way to intercept MicroSoft's auto-update?
> I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
> bug in this hotfix and Microsoft needs to know that.
> Thanks
> -FJ
Why not install the tools, allow the update or manually install the update
and then remove the tools?
Automatic updates are not something you would want on a production system so
you may want to turn them off, but the problem could still occur if you
turned them on at some point.
John
sql
every 3 hours. How shouyld I fix it.
Microsoft SQL Server 2005 Tools Express Edition -- Install started.
Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
installer has encountered an unexpected error. The error code is 2711. The
specified Feature name ('SQL_Documentation') not found in Feature table.
Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
not be installed. Error code 1603. Additional information is available in the
log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB932557_sql run_tools.msp.log.
Hi
"fj" wrote:
> Here are the errors in event log. The installation packeage keeps trying
> every 3 hours. How shouyld I fix it.
>
> Microsoft SQL Server 2005 Tools Express Edition -- Install started.
> Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
> installer has encountered an unexpected error. The error code is 2711. The
> specified Feature name ('SQL_Documentation') not found in Feature table.
> Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
> for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
> not be installed. Error code 1603. Additional information is available in the
> log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB932557_sql run_tools.msp.log.
What does this log say?
It may be similar to http://support.microsoft.com/kb/916760/en-us
or http://support.microsoft.com/kb/834484/en-us i.e. the permissions or
folders expected may not exist or have the wrong permissions or the account
doing the install may not have enough permissions.
John
|||Here is the part I found that might cause the problem. The specified Feature
name ('SQL_Documentation') not found in Feature table.
....
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E, Object:
C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a 1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget, Object:
C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
Express Edition -- Error 2711. The installer has encountered an unexpected
error. The error code is 2711. The specified Feature name
('SQL_Documentation') not found in Feature table.
Error 2711. The installer has encountered an unexpected error. The error
code is 2711. The specified Feature name ('SQL_Documentation') not found in
Feature table.
Action ended 9:51:03: CostFinalize. Return value 3.
Action ended 9:51:03: INSTALL. Return value 3.
Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Property(S): ProductLanguage = 1033
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.00.1399.06
Property(S): MEDIAPACKAGEPATH = \Setup\
....
|||Hi
"fj" wrote:
> Here is the part I found that might cause the problem. The specified Feature
> name ('SQL_Documentation') not found in Feature table.
>
> ...
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E, Object:
> C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a 1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget, Object:
> C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
> Express Edition -- Error 2711. The installer has encountered an unexpected
> error. The error code is 2711. The specified Feature name
> ('SQL_Documentation') not found in Feature table.
> Error 2711. The installer has encountered an unexpected error. The error
> code is 2711. The specified Feature name ('SQL_Documentation') not found in
> Feature table.
> Action ended 9:51:03: CostFinalize. Return value 3.
> Action ended 9:51:03: INSTALL. Return value 3.
> Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> Property(S): ProductLanguage = 1033
> Property(S): Manufacturer = Microsoft Corporation
> Property(S): ProductVersion = 9.00.1399.06
> Property(S): MEDIAPACKAGEPATH = \Setup\
> ...
SQL Express is not one of the products that have been listed as affected by
the hotfix!
http://support.microsoft.com/kb/932557/en-us
John
|||"John Bell" wrote:
> Hi
> "fj" wrote:
>
> SQL Express is not one of the products that have been listed as affected by
> the hotfix!
> http://support.microsoft.com/kb/932557/en-us
> John
Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
installed by auto-update.
Now it seems like there is a scheduled job at somewhere, how I can stop or
remove it?
Is the hotfix referred by your link a fix to the problem?
Thanks
-FJ
|||Hi
"fj" wrote:
>
> "John Bell" wrote:
>
> Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
> installed by auto-update.
> Now it seems like there is a scheduled job at somewhere, how I can stop or
> remove it?
> Is the hotfix referred by your link a fix to the problem?
> Thanks
> -FJ
It looks like you may have something left over then, if you have removed it.
You may want to check out:
http://msdn2.microsoft.com/en-us/vstudio/aa718704.aspx
or http://support.microsoft.com/kb/909967
John
|||Thanks John,
Actually I found the problem is because I didn't install the client tool and
documents from the original 2005 SQL Server(64bit). BUT, the auto-update
downloaded the hotfix for the SQL server 2005 without checking if I need this
fix. This hotfix (MSDN article number 932557) has "hardwired" update for
those tools and docs whch I don't have so the update failed.
Since the update is scheduled to launch every 3 hours, I am keep getting
this annoying errors.
Now my question still remains, how I can terminate the remaining update
manually? Is there a way to intercept MicroSoft's auto-update?
I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
bug in this hotfix and Microsoft needs to know that.
Thanks
-FJ
|||Hi
"fj" wrote:
> Thanks John,
> Actually I found the problem is because I didn't install the client tool and
> documents from the original 2005 SQL Server(64bit). BUT, the auto-update
> downloaded the hotfix for the SQL server 2005 without checking if I need this
> fix. This hotfix (MSDN article number 932557) has "hardwired" update for
> those tools and docs whch I don't have so the update failed.
> Since the update is scheduled to launch every 3 hours, I am keep getting
> this annoying errors.
> Now my question still remains, how I can terminate the remaining update
> manually? Is there a way to intercept MicroSoft's auto-update?
> I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
> bug in this hotfix and Microsoft needs to know that.
> Thanks
> -FJ
Why not install the tools, allow the update or manually install the update
and then remove the tools?
Automatic updates are not something you would want on a production system so
you may want to turn them off, but the problem could still occur if you
turned them on at some point.
John
sql
recent SQL 2005 hotfix creates problem
Here are the errors in event log. The installation packeage keeps trying
every 3 hours. How shouyld I fix it.
Microsoft SQL Server 2005 Tools Express Edition -- Install started.
Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
installer has encountered an unexpected error. The error code is 2711. The
specified Feature name ('SQL_Documentation') not found in Feature table.
Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
not be installed. Error code 1603. Additional information is available in th
e
log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB
932557_sqlrun_tools.msp.log.Hi
"fj" wrote:
> Here are the errors in event log. The installation packeage keeps trying
> every 3 hours. How shouyld I fix it.
>
> Microsoft SQL Server 2005 Tools Express Edition -- Install started.
> Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. Th
e
> installer has encountered an unexpected error. The error code is 2711. The
> specified Feature name ('SQL_Documentation') not found in Feature table.
> Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 140
6
> for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
> not be installed. Error code 1603. Additional information is available in
the
> log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB
932557_sqlrun_tools.msp.log.
What does this log say?
It may be similar to http://support.microsoft.com/kb/916760/en-us
or http://support.microsoft.com/kb/834484/en-us i.e. the permissions or
folders expected may not exist or have the wrong permissions or the account
doing the install may not have enough permissions.
John|||Here is the part I found that might cause the problem. The specified Feature
name ('SQL_Documentation') not found in Feature table.
...
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_
dc990e4797f81af1\
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
Express Edition -- Error 2711. The installer has encountered an unexpected
error. The error code is 2711. The specified Feature name
('SQL_Documentation') not found in Feature table.
Error 2711. The installer has encountered an unexpected error. The error
code is 2711. The specified Feature name ('SQL_Documentation') not found in
Feature table.
Action ended 9:51:03: CostFinalize. Return value 3.
Action ended 9:51:03: INSTALL. Return value 3.
Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Property(S): ProductLanguage = 1033
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.00.1399.06
Property(S): MEDIAPACKAGEPATH = \Setup\
...|||Hi
"fj" wrote:
> Here is the part I found that might cause the problem. The specified Featu
re
> name ('SQL_Documentation') not found in Feature table.
>
> ...
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
> C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_non
e_dc990e4797f81af1\
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object
:
> C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Too
ls
> Express Edition -- Error 2711. The installer has encountered an unexpected
> error. The error code is 2711. The specified Feature name
> ('SQL_Documentation') not found in Feature table.
> Error 2711. The installer has encountered an unexpected error. The error
> code is 2711. The specified Feature name ('SQL_Documentation') not found i
n
> Feature table.
> Action ended 9:51:03: CostFinalize. Return value 3.
> Action ended 9:51:03: INSTALL. Return value 3.
> Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> Property(S): ProductLanguage = 1033
> Property(S): Manufacturer = Microsoft Corporation
> Property(S): ProductVersion = 9.00.1399.06
> Property(S): MEDIAPACKAGEPATH = \Setup\
> ...
SQL Express is not one of the products that have been listed as affected by
the hotfix!
http://support.microsoft.com/kb/932557/en-us
John|||"John Bell" wrote:
> Hi
> "fj" wrote:
>
> SQL Express is not one of the products that have been listed as affected b
y
> the hotfix!
> http://support.microsoft.com/kb/932557/en-us
> John
Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
installed by auto-update.
Now it seems like there is a scheduled job at somewhere, how I can stop or
remove it?
Is the hotfix referred by your link a fix to the problem?
Thanks
-FJ|||Hi
"fj" wrote:
>
> "John Bell" wrote:
>
> Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix
is
> installed by auto-update.
> Now it seems like there is a scheduled job at somewhere, how I can stop or
> remove it?
> Is the hotfix referred by your link a fix to the problem?
> Thanks
> -FJ
It looks like you may have something left over then, if you have removed it.
You may want to check out:
http://msdn2.microsoft.com/en-us/vstudio/aa718704.aspx
or http://support.microsoft.com/kb/909967
John|||Thanks John,
Actually I found the problem is because I didn't install the client tool and
documents from the original 2005 SQL Server(64bit). BUT, the auto-update
downloaded the hotfix for the SQL server 2005 without checking if I need thi
s
fix. This hotfix (MSDN article number 932557) has "hardwired" update for
those tools and docs whch I don't have so the update failed.
Since the update is scheduled to launch every 3 hours, I am keep getting
this annoying errors.
Now my question still remains, how I can terminate the remaining update
manually? Is there a way to intercept MicroSoft's auto-update?
I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
bug in this hotfix and Microsoft needs to know that.
Thanks
-FJ|||Hi
"fj" wrote:
> Thanks John,
> Actually I found the problem is because I didn't install the client tool a
nd
> documents from the original 2005 SQL Server(64bit). BUT, the auto-update
> downloaded the hotfix for the SQL server 2005 without checking if I need t
his
> fix. This hotfix (MSDN article number 932557) has "hardwired" update for
> those tools and docs whch I don't have so the update failed.
> Since the update is scheduled to launch every 3 hours, I am keep getting
> this annoying errors.
> Now my question still remains, how I can terminate the remaining update
> manually? Is there a way to intercept MicroSoft's auto-update?
> I don't think I need to re-install or remove VS2005 or SQL 2005. There is
a
> bug in this hotfix and Microsoft needs to know that.
> Thanks
> -FJ
Why not install the tools, allow the update or manually install the update
and then remove the tools?
Automatic updates are not something you would want on a production system so
you may want to turn them off, but the problem could still occur if you
turned them on at some point.
John
every 3 hours. How shouyld I fix it.
Microsoft SQL Server 2005 Tools Express Edition -- Install started.
Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
installer has encountered an unexpected error. The error code is 2711. The
specified Feature name ('SQL_Documentation') not found in Feature table.
Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
not be installed. Error code 1603. Additional information is available in th
e
log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB
932557_sqlrun_tools.msp.log.Hi
"fj" wrote:
> Here are the errors in event log. The installation packeage keeps trying
> every 3 hours. How shouyld I fix it.
>
> Microsoft SQL Server 2005 Tools Express Edition -- Install started.
> Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. Th
e
> installer has encountered an unexpected error. The error code is 2711. The
> specified Feature name ('SQL_Documentation') not found in Feature table.
> Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 140
6
> for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
> not be installed. Error code 1603. Additional information is available in
the
> log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB
932557_sqlrun_tools.msp.log.
What does this log say?
It may be similar to http://support.microsoft.com/kb/916760/en-us
or http://support.microsoft.com/kb/834484/en-us i.e. the permissions or
folders expected may not exist or have the wrong permissions or the account
doing the install may not have enough permissions.
John|||Here is the part I found that might cause the problem. The specified Feature
name ('SQL_Documentation') not found in Feature table.
...
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_
dc990e4797f81af1\
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
Express Edition -- Error 2711. The installer has encountered an unexpected
error. The error code is 2711. The specified Feature name
('SQL_Documentation') not found in Feature table.
Error 2711. The installer has encountered an unexpected error. The error
code is 2711. The specified Feature name ('SQL_Documentation') not found in
Feature table.
Action ended 9:51:03: CostFinalize. Return value 3.
Action ended 9:51:03: INSTALL. Return value 3.
Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Property(S): ProductLanguage = 1033
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.00.1399.06
Property(S): MEDIAPACKAGEPATH = \Setup\
...|||Hi
"fj" wrote:
> Here is the part I found that might cause the problem. The specified Featu
re
> name ('SQL_Documentation') not found in Feature table.
>
> ...
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
> C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_non
e_dc990e4797f81af1\
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object
:
> C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Too
ls
> Express Edition -- Error 2711. The installer has encountered an unexpected
> error. The error code is 2711. The specified Feature name
> ('SQL_Documentation') not found in Feature table.
> Error 2711. The installer has encountered an unexpected error. The error
> code is 2711. The specified Feature name ('SQL_Documentation') not found i
n
> Feature table.
> Action ended 9:51:03: CostFinalize. Return value 3.
> Action ended 9:51:03: INSTALL. Return value 3.
> Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> Property(S): ProductLanguage = 1033
> Property(S): Manufacturer = Microsoft Corporation
> Property(S): ProductVersion = 9.00.1399.06
> Property(S): MEDIAPACKAGEPATH = \Setup\
> ...
SQL Express is not one of the products that have been listed as affected by
the hotfix!
http://support.microsoft.com/kb/932557/en-us
John|||"John Bell" wrote:
> Hi
> "fj" wrote:
>
> SQL Express is not one of the products that have been listed as affected b
y
> the hotfix!
> http://support.microsoft.com/kb/932557/en-us
> John
Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
installed by auto-update.
Now it seems like there is a scheduled job at somewhere, how I can stop or
remove it?
Is the hotfix referred by your link a fix to the problem?
Thanks
-FJ|||Hi
"fj" wrote:
>
> "John Bell" wrote:
>
> Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix
is
> installed by auto-update.
> Now it seems like there is a scheduled job at somewhere, how I can stop or
> remove it?
> Is the hotfix referred by your link a fix to the problem?
> Thanks
> -FJ
It looks like you may have something left over then, if you have removed it.
You may want to check out:
http://msdn2.microsoft.com/en-us/vstudio/aa718704.aspx
or http://support.microsoft.com/kb/909967
John|||Thanks John,
Actually I found the problem is because I didn't install the client tool and
documents from the original 2005 SQL Server(64bit). BUT, the auto-update
downloaded the hotfix for the SQL server 2005 without checking if I need thi
s
fix. This hotfix (MSDN article number 932557) has "hardwired" update for
those tools and docs whch I don't have so the update failed.
Since the update is scheduled to launch every 3 hours, I am keep getting
this annoying errors.
Now my question still remains, how I can terminate the remaining update
manually? Is there a way to intercept MicroSoft's auto-update?
I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
bug in this hotfix and Microsoft needs to know that.
Thanks
-FJ|||Hi
"fj" wrote:
> Thanks John,
> Actually I found the problem is because I didn't install the client tool a
nd
> documents from the original 2005 SQL Server(64bit). BUT, the auto-update
> downloaded the hotfix for the SQL server 2005 without checking if I need t
his
> fix. This hotfix (MSDN article number 932557) has "hardwired" update for
> those tools and docs whch I don't have so the update failed.
> Since the update is scheduled to launch every 3 hours, I am keep getting
> this annoying errors.
> Now my question still remains, how I can terminate the remaining update
> manually? Is there a way to intercept MicroSoft's auto-update?
> I don't think I need to re-install or remove VS2005 or SQL 2005. There is
a
> bug in this hotfix and Microsoft needs to know that.
> Thanks
> -FJ
Why not install the tools, allow the update or manually install the update
and then remove the tools?
Automatic updates are not something you would want on a production system so
you may want to turn them off, but the problem could still occur if you
turned them on at some point.
John
recent SQL 2005 hotfix creates problem
Here are the errors in event log. The installation packeage keeps trying
every 3 hours. How shouyld I fix it.
Microsoft SQL Server 2005 Tools Express Edition -- Install started.
Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
installer has encountered an unexpected error. The error code is 2711. The
specified Feature name ('SQL_Documentation') not found in Feature table.
Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
not be installed. Error code 1603. Additional information is available in the
log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB932557_sqlrun_tools.msp.log.Hi
"fj" wrote:
> Here are the errors in event log. The installation packeage keeps trying
> every 3 hours. How shouyld I fix it.
>
> Microsoft SQL Server 2005 Tools Express Edition -- Install started.
> Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
> installer has encountered an unexpected error. The error code is 2711. The
> specified Feature name ('SQL_Documentation') not found in Feature table.
> Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
> for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
> not be installed. Error code 1603. Additional information is available in the
> log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB932557_sqlrun_tools.msp.log.
What does this log say?
It may be similar to http://support.microsoft.com/kb/916760/en-us
or http://support.microsoft.com/kb/834484/en-us i.e. the permissions or
folders expected may not exist or have the wrong permissions or the account
doing the install may not have enough permissions.
John|||Here is the part I found that might cause the problem. The specified Feature
name ('SQL_Documentation') not found in Feature table.
...
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
Express Edition -- Error 2711. The installer has encountered an unexpected
error. The error code is 2711. The specified Feature name
('SQL_Documentation') not found in Feature table.
Error 2711. The installer has encountered an unexpected error. The error
code is 2711. The specified Feature name ('SQL_Documentation') not found in
Feature table.
Action ended 9:51:03: CostFinalize. Return value 3.
Action ended 9:51:03: INSTALL. Return value 3.
Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Property(S): ProductLanguage = 1033
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.00.1399.06
Property(S): MEDIAPACKAGEPATH = \Setup\
...|||Hi
"fj" wrote:
> Here is the part I found that might cause the problem. The specified Feature
> name ('SQL_Documentation') not found in Feature table.
>
> ...
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
> C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
> C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
> Express Edition -- Error 2711. The installer has encountered an unexpected
> error. The error code is 2711. The specified Feature name
> ('SQL_Documentation') not found in Feature table.
> Error 2711. The installer has encountered an unexpected error. The error
> code is 2711. The specified Feature name ('SQL_Documentation') not found in
> Feature table.
> Action ended 9:51:03: CostFinalize. Return value 3.
> Action ended 9:51:03: INSTALL. Return value 3.
> Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> Property(S): ProductLanguage = 1033
> Property(S): Manufacturer = Microsoft Corporation
> Property(S): ProductVersion = 9.00.1399.06
> Property(S): MEDIAPACKAGEPATH = \Setup\
> ...
SQL Express is not one of the products that have been listed as affected by
the hotfix!
http://support.microsoft.com/kb/932557/en-us
John|||"John Bell" wrote:
> Hi
> "fj" wrote:
> > Here is the part I found that might cause the problem. The specified Feature
> > name ('SQL_Documentation') not found in Feature table.
> >
> >
> >
> > ...
> > MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> > payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
> > C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
> > MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
> > C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> > MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> > MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
> > Express Edition -- Error 2711. The installer has encountered an unexpected
> > error. The error code is 2711. The specified Feature name
> > ('SQL_Documentation') not found in Feature table.
> >
> > Error 2711. The installer has encountered an unexpected error. The error
> > code is 2711. The specified Feature name ('SQL_Documentation') not found in
> > Feature table.
> > Action ended 9:51:03: CostFinalize. Return value 3.
> > Action ended 9:51:03: INSTALL. Return value 3.
> > Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> > Property(S): ProductLanguage = 1033
> > Property(S): Manufacturer = Microsoft Corporation
> > Property(S): ProductVersion = 9.00.1399.06
> > Property(S): MEDIAPACKAGEPATH = \Setup\
> > ...
> SQL Express is not one of the products that have been listed as affected by
> the hotfix!
> http://support.microsoft.com/kb/932557/en-us
> John
Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
installed by auto-update.
Now it seems like there is a scheduled job at somewhere, how I can stop or
remove it?
Is the hotfix referred by your link a fix to the problem?
Thanks
-FJ|||Hi
"fj" wrote:
>
> "John Bell" wrote:
> > Hi
> >
> > "fj" wrote:
> >
> > > Here is the part I found that might cause the problem. The specified Feature
> > > name ('SQL_Documentation') not found in Feature table.
> > >
> > >
> > >
> > > ...
> > > MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> > > payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
> > > C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
> > > MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
> > > C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> > > MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> > > MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
> > > Express Edition -- Error 2711. The installer has encountered an unexpected
> > > error. The error code is 2711. The specified Feature name
> > > ('SQL_Documentation') not found in Feature table.
> > >
> > > Error 2711. The installer has encountered an unexpected error. The error
> > > code is 2711. The specified Feature name ('SQL_Documentation') not found in
> > > Feature table.
> > > Action ended 9:51:03: CostFinalize. Return value 3.
> > > Action ended 9:51:03: INSTALL. Return value 3.
> > > Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> > > Property(S): ProductLanguage = 1033
> > > Property(S): Manufacturer = Microsoft Corporation
> > > Property(S): ProductVersion = 9.00.1399.06
> > > Property(S): MEDIAPACKAGEPATH = \Setup\
> > > ...
> >
> > SQL Express is not one of the products that have been listed as affected by
> > the hotfix!
> > http://support.microsoft.com/kb/932557/en-us
> >
> > John
> Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
> installed by auto-update.
> Now it seems like there is a scheduled job at somewhere, how I can stop or
> remove it?
> Is the hotfix referred by your link a fix to the problem?
> Thanks
> -FJ
It looks like you may have something left over then, if you have removed it.
You may want to check out:
http://msdn2.microsoft.com/en-us/vstudio/aa718704.aspx
or http://support.microsoft.com/kb/909967
John|||Thanks John,
Actually I found the problem is because I didn't install the client tool and
documents from the original 2005 SQL Server(64bit). BUT, the auto-update
downloaded the hotfix for the SQL server 2005 without checking if I need this
fix. This hotfix (MSDN article number 932557) has "hardwired" update for
those tools and docs whch I don't have so the update failed.
Since the update is scheduled to launch every 3 hours, I am keep getting
this annoying errors.
Now my question still remains, how I can terminate the remaining update
manually? Is there a way to intercept MicroSoft's auto-update?
I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
bug in this hotfix and Microsoft needs to know that.
Thanks
-FJ|||Hi
"fj" wrote:
> Thanks John,
> Actually I found the problem is because I didn't install the client tool and
> documents from the original 2005 SQL Server(64bit). BUT, the auto-update
> downloaded the hotfix for the SQL server 2005 without checking if I need this
> fix. This hotfix (MSDN article number 932557) has "hardwired" update for
> those tools and docs whch I don't have so the update failed.
> Since the update is scheduled to launch every 3 hours, I am keep getting
> this annoying errors.
> Now my question still remains, how I can terminate the remaining update
> manually? Is there a way to intercept MicroSoft's auto-update?
> I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
> bug in this hotfix and Microsoft needs to know that.
> Thanks
> -FJ
Why not install the tools, allow the update or manually install the update
and then remove the tools?
Automatic updates are not something you would want on a production system so
you may want to turn them off, but the problem could still occur if you
turned them on at some point.
John
every 3 hours. How shouyld I fix it.
Microsoft SQL Server 2005 Tools Express Edition -- Install started.
Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
installer has encountered an unexpected error. The error code is 2711. The
specified Feature name ('SQL_Documentation') not found in Feature table.
Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
not be installed. Error code 1603. Additional information is available in the
log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB932557_sqlrun_tools.msp.log.Hi
"fj" wrote:
> Here are the errors in event log. The installation packeage keeps trying
> every 3 hours. How shouyld I fix it.
>
> Microsoft SQL Server 2005 Tools Express Edition -- Install started.
> Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
> installer has encountered an unexpected error. The error code is 2711. The
> specified Feature name ('SQL_Documentation') not found in Feature table.
> Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
> for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
> not be installed. Error code 1603. Additional information is available in the
> log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB932557_sqlrun_tools.msp.log.
What does this log say?
It may be similar to http://support.microsoft.com/kb/916760/en-us
or http://support.microsoft.com/kb/834484/en-us i.e. the permissions or
folders expected may not exist or have the wrong permissions or the account
doing the install may not have enough permissions.
John|||Here is the part I found that might cause the problem. The specified Feature
name ('SQL_Documentation') not found in Feature table.
...
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
Express Edition -- Error 2711. The installer has encountered an unexpected
error. The error code is 2711. The specified Feature name
('SQL_Documentation') not found in Feature table.
Error 2711. The installer has encountered an unexpected error. The error
code is 2711. The specified Feature name ('SQL_Documentation') not found in
Feature table.
Action ended 9:51:03: CostFinalize. Return value 3.
Action ended 9:51:03: INSTALL. Return value 3.
Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Property(S): ProductLanguage = 1033
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.00.1399.06
Property(S): MEDIAPACKAGEPATH = \Setup\
...|||Hi
"fj" wrote:
> Here is the part I found that might cause the problem. The specified Feature
> name ('SQL_Documentation') not found in Feature table.
>
> ...
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
> C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
> C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
> Express Edition -- Error 2711. The installer has encountered an unexpected
> error. The error code is 2711. The specified Feature name
> ('SQL_Documentation') not found in Feature table.
> Error 2711. The installer has encountered an unexpected error. The error
> code is 2711. The specified Feature name ('SQL_Documentation') not found in
> Feature table.
> Action ended 9:51:03: CostFinalize. Return value 3.
> Action ended 9:51:03: INSTALL. Return value 3.
> Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> Property(S): ProductLanguage = 1033
> Property(S): Manufacturer = Microsoft Corporation
> Property(S): ProductVersion = 9.00.1399.06
> Property(S): MEDIAPACKAGEPATH = \Setup\
> ...
SQL Express is not one of the products that have been listed as affected by
the hotfix!
http://support.microsoft.com/kb/932557/en-us
John|||"John Bell" wrote:
> Hi
> "fj" wrote:
> > Here is the part I found that might cause the problem. The specified Feature
> > name ('SQL_Documentation') not found in Feature table.
> >
> >
> >
> > ...
> > MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> > payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
> > C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
> > MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
> > C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> > MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> > MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
> > Express Edition -- Error 2711. The installer has encountered an unexpected
> > error. The error code is 2711. The specified Feature name
> > ('SQL_Documentation') not found in Feature table.
> >
> > Error 2711. The installer has encountered an unexpected error. The error
> > code is 2711. The specified Feature name ('SQL_Documentation') not found in
> > Feature table.
> > Action ended 9:51:03: CostFinalize. Return value 3.
> > Action ended 9:51:03: INSTALL. Return value 3.
> > Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> > Property(S): ProductLanguage = 1033
> > Property(S): Manufacturer = Microsoft Corporation
> > Property(S): ProductVersion = 9.00.1399.06
> > Property(S): MEDIAPACKAGEPATH = \Setup\
> > ...
> SQL Express is not one of the products that have been listed as affected by
> the hotfix!
> http://support.microsoft.com/kb/932557/en-us
> John
Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
installed by auto-update.
Now it seems like there is a scheduled job at somewhere, how I can stop or
remove it?
Is the hotfix referred by your link a fix to the problem?
Thanks
-FJ|||Hi
"fj" wrote:
>
> "John Bell" wrote:
> > Hi
> >
> > "fj" wrote:
> >
> > > Here is the part I found that might cause the problem. The specified Feature
> > > name ('SQL_Documentation') not found in Feature table.
> > >
> > >
> > >
> > > ...
> > > MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> > > payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
> > > C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
> > > MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
> > > C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> > > MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> > > MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
> > > Express Edition -- Error 2711. The installer has encountered an unexpected
> > > error. The error code is 2711. The specified Feature name
> > > ('SQL_Documentation') not found in Feature table.
> > >
> > > Error 2711. The installer has encountered an unexpected error. The error
> > > code is 2711. The specified Feature name ('SQL_Documentation') not found in
> > > Feature table.
> > > Action ended 9:51:03: CostFinalize. Return value 3.
> > > Action ended 9:51:03: INSTALL. Return value 3.
> > > Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> > > Property(S): ProductLanguage = 1033
> > > Property(S): Manufacturer = Microsoft Corporation
> > > Property(S): ProductVersion = 9.00.1399.06
> > > Property(S): MEDIAPACKAGEPATH = \Setup\
> > > ...
> >
> > SQL Express is not one of the products that have been listed as affected by
> > the hotfix!
> > http://support.microsoft.com/kb/932557/en-us
> >
> > John
> Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
> installed by auto-update.
> Now it seems like there is a scheduled job at somewhere, how I can stop or
> remove it?
> Is the hotfix referred by your link a fix to the problem?
> Thanks
> -FJ
It looks like you may have something left over then, if you have removed it.
You may want to check out:
http://msdn2.microsoft.com/en-us/vstudio/aa718704.aspx
or http://support.microsoft.com/kb/909967
John|||Thanks John,
Actually I found the problem is because I didn't install the client tool and
documents from the original 2005 SQL Server(64bit). BUT, the auto-update
downloaded the hotfix for the SQL server 2005 without checking if I need this
fix. This hotfix (MSDN article number 932557) has "hardwired" update for
those tools and docs whch I don't have so the update failed.
Since the update is scheduled to launch every 3 hours, I am keep getting
this annoying errors.
Now my question still remains, how I can terminate the remaining update
manually? Is there a way to intercept MicroSoft's auto-update?
I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
bug in this hotfix and Microsoft needs to know that.
Thanks
-FJ|||Hi
"fj" wrote:
> Thanks John,
> Actually I found the problem is because I didn't install the client tool and
> documents from the original 2005 SQL Server(64bit). BUT, the auto-update
> downloaded the hotfix for the SQL server 2005 without checking if I need this
> fix. This hotfix (MSDN article number 932557) has "hardwired" update for
> those tools and docs whch I don't have so the update failed.
> Since the update is scheduled to launch every 3 hours, I am keep getting
> this annoying errors.
> Now my question still remains, how I can terminate the remaining update
> manually? Is there a way to intercept MicroSoft's auto-update?
> I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
> bug in this hotfix and Microsoft needs to know that.
> Thanks
> -FJ
Why not install the tools, allow the update or manually install the update
and then remove the tools?
Automatic updates are not something you would want on a production system so
you may want to turn them off, but the problem could still occur if you
turned them on at some point.
John
Recent Creating View
I know that most of the persons could not get me exactly
so i am again going to clarify my problem.
I want to create tables and views from inside the VB-code
using SQL-script. I can do this by reading a text (script)
file, storing the string in a variable say MYSQLSTR and
running it like CN.EXECUTE MYSQLSTR inside my code. Now I
have created the sql-script from enterprise manager which
includes GO for each create statement of the table. I run
it from inside my VB-Code. error raised which says 'GO' is
not recognizable. OK. I removed 'GO' from the file and run
it again as i described above. It is running fine and
creating tables in the database. This file, after removing
all the 'GOs' runs inside the query analyser too.
Now when I do this with VIEWS, same problems come and I
remove 'GO' but this time it says like (even inside query
analyser):
Server: Msg 156, Level 15, State 1, Procedure View1, Line
10
Incorrect syntax near the keyword 'SET'.
Server: Msg 111, Level 15, State 1, Procedure DmView1,
Line 16
'CREATE VIEW' must be the first statement in a query batch.
Now I have to create views at one go as i create all the
tables at one go by running the SQL-script through my code.
ur suggestions are welcome.
Billi98Please don't re-post. I provided an answer in your prior post.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"billi98" <anonymous@.discussions.microsoft.com> wrote in message
news:4c1001c42c3e$3d1d2050$a301280a@.phx.gbl...
> I know that most of the persons could not get me exactly
> so i am again going to clarify my problem.
> I want to create tables and views from inside the VB-code
> using SQL-script. I can do this by reading a text (script)
> file, storing the string in a variable say MYSQLSTR and
> running it like CN.EXECUTE MYSQLSTR inside my code. Now I
> have created the sql-script from enterprise manager which
> includes GO for each create statement of the table. I run
> it from inside my VB-Code. error raised which says 'GO' is
> not recognizable. OK. I removed 'GO' from the file and run
> it again as i described above. It is running fine and
> creating tables in the database. This file, after removing
> all the 'GOs' runs inside the query analyser too.
> Now when I do this with VIEWS, same problems come and I
> remove 'GO' but this time it says like (even inside query
> analyser):
> Server: Msg 156, Level 15, State 1, Procedure View1, Line
> 10
> Incorrect syntax near the keyword 'SET'.
> Server: Msg 111, Level 15, State 1, Procedure DmView1,
> Line 16
> 'CREATE VIEW' must be the first statement in a query batch.
> Now I have to create views at one go as i create all the
> tables at one go by running the SQL-script through my code.
> ur suggestions are welcome.
> Billi98
>|||Hi Bill,
Ok then 'Why the go statement didn't work'
The reason is that the GO statement only works through
osql and isql (or in this case Query Analyser), as your
running this through VB, the go statement isn't supported
so it doesn't work.
The second error is a standard sql error, which I don't
think has anything to do with the go statement.
Could you possibly post the first 30 lines of your code ?
Thanks
J
>--Original Message--
>I know that most of the persons could not get me exactly
>so i am again going to clarify my problem.
>I want to create tables and views from inside the VB-code
>using SQL-script. I can do this by reading a text
(script)
>file, storing the string in a variable say MYSQLSTR and
>running it like CN.EXECUTE MYSQLSTR inside my code. Now I
>have created the sql-script from enterprise manager which
>includes GO for each create statement of the table. I run
>it from inside my VB-Code. error raised which says 'GO'
is
>not recognizable. OK. I removed 'GO' from the file and
run
>it again as i described above. It is running fine and
>creating tables in the database. This file, after
removing
>all the 'GOs' runs inside the query analyser too.
>Now when I do this with VIEWS, same problems come and I
>remove 'GO' but this time it says like (even inside query
>analyser):
>Server: Msg 156, Level 15, State 1, Procedure View1, Line
>10
>Incorrect syntax near the keyword 'SET'.
>Server: Msg 111, Level 15, State 1, Procedure DmView1,
>Line 16
>'CREATE VIEW' must be the first statement in a query
batch.
>Now I have to create views at one go as i create all the
>tables at one go by running the SQL-script through my
code.
>ur suggestions are welcome.
>Billi98
>.
>
so i am again going to clarify my problem.
I want to create tables and views from inside the VB-code
using SQL-script. I can do this by reading a text (script)
file, storing the string in a variable say MYSQLSTR and
running it like CN.EXECUTE MYSQLSTR inside my code. Now I
have created the sql-script from enterprise manager which
includes GO for each create statement of the table. I run
it from inside my VB-Code. error raised which says 'GO' is
not recognizable. OK. I removed 'GO' from the file and run
it again as i described above. It is running fine and
creating tables in the database. This file, after removing
all the 'GOs' runs inside the query analyser too.
Now when I do this with VIEWS, same problems come and I
remove 'GO' but this time it says like (even inside query
analyser):
Server: Msg 156, Level 15, State 1, Procedure View1, Line
10
Incorrect syntax near the keyword 'SET'.
Server: Msg 111, Level 15, State 1, Procedure DmView1,
Line 16
'CREATE VIEW' must be the first statement in a query batch.
Now I have to create views at one go as i create all the
tables at one go by running the SQL-script through my code.
ur suggestions are welcome.
Billi98Please don't re-post. I provided an answer in your prior post.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"billi98" <anonymous@.discussions.microsoft.com> wrote in message
news:4c1001c42c3e$3d1d2050$a301280a@.phx.gbl...
> I know that most of the persons could not get me exactly
> so i am again going to clarify my problem.
> I want to create tables and views from inside the VB-code
> using SQL-script. I can do this by reading a text (script)
> file, storing the string in a variable say MYSQLSTR and
> running it like CN.EXECUTE MYSQLSTR inside my code. Now I
> have created the sql-script from enterprise manager which
> includes GO for each create statement of the table. I run
> it from inside my VB-Code. error raised which says 'GO' is
> not recognizable. OK. I removed 'GO' from the file and run
> it again as i described above. It is running fine and
> creating tables in the database. This file, after removing
> all the 'GOs' runs inside the query analyser too.
> Now when I do this with VIEWS, same problems come and I
> remove 'GO' but this time it says like (even inside query
> analyser):
> Server: Msg 156, Level 15, State 1, Procedure View1, Line
> 10
> Incorrect syntax near the keyword 'SET'.
> Server: Msg 111, Level 15, State 1, Procedure DmView1,
> Line 16
> 'CREATE VIEW' must be the first statement in a query batch.
> Now I have to create views at one go as i create all the
> tables at one go by running the SQL-script through my code.
> ur suggestions are welcome.
> Billi98
>|||Hi Bill,
Ok then 'Why the go statement didn't work'
The reason is that the GO statement only works through
osql and isql (or in this case Query Analyser), as your
running this through VB, the go statement isn't supported
so it doesn't work.
The second error is a standard sql error, which I don't
think has anything to do with the go statement.
Could you possibly post the first 30 lines of your code ?
Thanks
J
>--Original Message--
>I know that most of the persons could not get me exactly
>so i am again going to clarify my problem.
>I want to create tables and views from inside the VB-code
>using SQL-script. I can do this by reading a text
(script)
>file, storing the string in a variable say MYSQLSTR and
>running it like CN.EXECUTE MYSQLSTR inside my code. Now I
>have created the sql-script from enterprise manager which
>includes GO for each create statement of the table. I run
>it from inside my VB-Code. error raised which says 'GO'
is
>not recognizable. OK. I removed 'GO' from the file and
run
>it again as i described above. It is running fine and
>creating tables in the database. This file, after
removing
>all the 'GOs' runs inside the query analyser too.
>Now when I do this with VIEWS, same problems come and I
>remove 'GO' but this time it says like (even inside query
>analyser):
>Server: Msg 156, Level 15, State 1, Procedure View1, Line
>10
>Incorrect syntax near the keyword 'SET'.
>Server: Msg 111, Level 15, State 1, Procedure DmView1,
>Line 16
>'CREATE VIEW' must be the first statement in a query
batch.
>Now I have to create views at one go as i create all the
>tables at one go by running the SQL-script through my
code.
>ur suggestions are welcome.
>Billi98
>.
>
Recent Creating View
I know that most of the persons could not get me exactly
so i am again going to clarify my problem.
I want to create tables and views from inside the VB-code
using SQL-script. I can do this by reading a text (script)
file, storing the string in a variable say MYSQLSTR and
running it like CN.EXECUTE MYSQLSTR inside my code. Now I
have created the sql-script from enterprise manager which
includes GO for each create statement of the table. I run
it from inside my VB-Code. error raised which says 'GO' is
not recognizable. OK. I removed 'GO' from the file and run
it again as i described above. It is running fine and
creating tables in the database. This file, after removing
all the 'GOs' runs inside the query analyser too.
Now when I do this with VIEWS, same problems come and I
remove 'GO' but this time it says like (even inside query
analyser):
Server: Msg 156, Level 15, State 1, Procedure View1, Line
10
Incorrect syntax near the keyword 'SET'.
Server: Msg 111, Level 15, State 1, Procedure DmView1,
Line 16
'CREATE VIEW' must be the first statement in a query batch.
Now I have to create views at one go as i create all the
tables at one go by running the SQL-script through my code.
ur suggestions are welcome.
Billi98
Please don't re-post. I provided an answer in your prior post.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"billi98" <anonymous@.discussions.microsoft.com> wrote in message
news:4c1001c42c3e$3d1d2050$a301280a@.phx.gbl...
> I know that most of the persons could not get me exactly
> so i am again going to clarify my problem.
> I want to create tables and views from inside the VB-code
> using SQL-script. I can do this by reading a text (script)
> file, storing the string in a variable say MYSQLSTR and
> running it like CN.EXECUTE MYSQLSTR inside my code. Now I
> have created the sql-script from enterprise manager which
> includes GO for each create statement of the table. I run
> it from inside my VB-Code. error raised which says 'GO' is
> not recognizable. OK. I removed 'GO' from the file and run
> it again as i described above. It is running fine and
> creating tables in the database. This file, after removing
> all the 'GOs' runs inside the query analyser too.
> Now when I do this with VIEWS, same problems come and I
> remove 'GO' but this time it says like (even inside query
> analyser):
> Server: Msg 156, Level 15, State 1, Procedure View1, Line
> 10
> Incorrect syntax near the keyword 'SET'.
> Server: Msg 111, Level 15, State 1, Procedure DmView1,
> Line 16
> 'CREATE VIEW' must be the first statement in a query batch.
> Now I have to create views at one go as i create all the
> tables at one go by running the SQL-script through my code.
> ur suggestions are welcome.
> Billi98
>
so i am again going to clarify my problem.
I want to create tables and views from inside the VB-code
using SQL-script. I can do this by reading a text (script)
file, storing the string in a variable say MYSQLSTR and
running it like CN.EXECUTE MYSQLSTR inside my code. Now I
have created the sql-script from enterprise manager which
includes GO for each create statement of the table. I run
it from inside my VB-Code. error raised which says 'GO' is
not recognizable. OK. I removed 'GO' from the file and run
it again as i described above. It is running fine and
creating tables in the database. This file, after removing
all the 'GOs' runs inside the query analyser too.
Now when I do this with VIEWS, same problems come and I
remove 'GO' but this time it says like (even inside query
analyser):
Server: Msg 156, Level 15, State 1, Procedure View1, Line
10
Incorrect syntax near the keyword 'SET'.
Server: Msg 111, Level 15, State 1, Procedure DmView1,
Line 16
'CREATE VIEW' must be the first statement in a query batch.
Now I have to create views at one go as i create all the
tables at one go by running the SQL-script through my code.
ur suggestions are welcome.
Billi98
Please don't re-post. I provided an answer in your prior post.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"billi98" <anonymous@.discussions.microsoft.com> wrote in message
news:4c1001c42c3e$3d1d2050$a301280a@.phx.gbl...
> I know that most of the persons could not get me exactly
> so i am again going to clarify my problem.
> I want to create tables and views from inside the VB-code
> using SQL-script. I can do this by reading a text (script)
> file, storing the string in a variable say MYSQLSTR and
> running it like CN.EXECUTE MYSQLSTR inside my code. Now I
> have created the sql-script from enterprise manager which
> includes GO for each create statement of the table. I run
> it from inside my VB-Code. error raised which says 'GO' is
> not recognizable. OK. I removed 'GO' from the file and run
> it again as i described above. It is running fine and
> creating tables in the database. This file, after removing
> all the 'GOs' runs inside the query analyser too.
> Now when I do this with VIEWS, same problems come and I
> remove 'GO' but this time it says like (even inside query
> analyser):
> Server: Msg 156, Level 15, State 1, Procedure View1, Line
> 10
> Incorrect syntax near the keyword 'SET'.
> Server: Msg 111, Level 15, State 1, Procedure DmView1,
> Line 16
> 'CREATE VIEW' must be the first statement in a query batch.
> Now I have to create views at one go as i create all the
> tables at one go by running the SQL-script through my code.
> ur suggestions are welcome.
> Billi98
>
Recent Creating View
I know that most of the persons could not get me exactly
so i am again going to clarify my problem.
I want to create tables and views from inside the VB-code
using SQL-script. I can do this by reading a text (script)
file, storing the string in a variable say MYSQLSTR and
running it like CN.EXECUTE MYSQLSTR inside my code. Now I
have created the sql-script from enterprise manager which
includes GO for each create statement of the table. I run
it from inside my VB-Code. error raised which says 'GO' is
not recognizable. OK. I removed 'GO' from the file and run
it again as i described above. It is running fine and
creating tables in the database. This file, after removing
all the 'GOs' runs inside the query analyser too.
Now when I do this with VIEWS, same problems come and I
remove 'GO' but this time it says like (even inside query
analyser):
Server: Msg 156, Level 15, State 1, Procedure View1, Line
10
Incorrect syntax near the keyword 'SET'.
Server: Msg 111, Level 15, State 1, Procedure DmView1,
Line 16
'CREATE VIEW' must be the first statement in a query batch.
Now I have to create views at one go as i create all the
tables at one go by running the SQL-script through my code.
ur suggestions are welcome.
Billi98Please don't re-post. I provided an answer in your prior post.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"billi98" <anonymous@.discussions.microsoft.com> wrote in message
news:4c1001c42c3e$3d1d2050$a301280a@.phx.gbl...
> I know that most of the persons could not get me exactly
> so i am again going to clarify my problem.
> I want to create tables and views from inside the VB-code
> using SQL-script. I can do this by reading a text (script)
> file, storing the string in a variable say MYSQLSTR and
> running it like CN.EXECUTE MYSQLSTR inside my code. Now I
> have created the sql-script from enterprise manager which
> includes GO for each create statement of the table. I run
> it from inside my VB-Code. error raised which says 'GO' is
> not recognizable. OK. I removed 'GO' from the file and run
> it again as i described above. It is running fine and
> creating tables in the database. This file, after removing
> all the 'GOs' runs inside the query analyser too.
> Now when I do this with VIEWS, same problems come and I
> remove 'GO' but this time it says like (even inside query
> analyser):
> Server: Msg 156, Level 15, State 1, Procedure View1, Line
> 10
> Incorrect syntax near the keyword 'SET'.
> Server: Msg 111, Level 15, State 1, Procedure DmView1,
> Line 16
> 'CREATE VIEW' must be the first statement in a query batch.
> Now I have to create views at one go as i create all the
> tables at one go by running the SQL-script through my code.
> ur suggestions are welcome.
> Billi98
>sql
so i am again going to clarify my problem.
I want to create tables and views from inside the VB-code
using SQL-script. I can do this by reading a text (script)
file, storing the string in a variable say MYSQLSTR and
running it like CN.EXECUTE MYSQLSTR inside my code. Now I
have created the sql-script from enterprise manager which
includes GO for each create statement of the table. I run
it from inside my VB-Code. error raised which says 'GO' is
not recognizable. OK. I removed 'GO' from the file and run
it again as i described above. It is running fine and
creating tables in the database. This file, after removing
all the 'GOs' runs inside the query analyser too.
Now when I do this with VIEWS, same problems come and I
remove 'GO' but this time it says like (even inside query
analyser):
Server: Msg 156, Level 15, State 1, Procedure View1, Line
10
Incorrect syntax near the keyword 'SET'.
Server: Msg 111, Level 15, State 1, Procedure DmView1,
Line 16
'CREATE VIEW' must be the first statement in a query batch.
Now I have to create views at one go as i create all the
tables at one go by running the SQL-script through my code.
ur suggestions are welcome.
Billi98Please don't re-post. I provided an answer in your prior post.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"billi98" <anonymous@.discussions.microsoft.com> wrote in message
news:4c1001c42c3e$3d1d2050$a301280a@.phx.gbl...
> I know that most of the persons could not get me exactly
> so i am again going to clarify my problem.
> I want to create tables and views from inside the VB-code
> using SQL-script. I can do this by reading a text (script)
> file, storing the string in a variable say MYSQLSTR and
> running it like CN.EXECUTE MYSQLSTR inside my code. Now I
> have created the sql-script from enterprise manager which
> includes GO for each create statement of the table. I run
> it from inside my VB-Code. error raised which says 'GO' is
> not recognizable. OK. I removed 'GO' from the file and run
> it again as i described above. It is running fine and
> creating tables in the database. This file, after removing
> all the 'GOs' runs inside the query analyser too.
> Now when I do this with VIEWS, same problems come and I
> remove 'GO' but this time it says like (even inside query
> analyser):
> Server: Msg 156, Level 15, State 1, Procedure View1, Line
> 10
> Incorrect syntax near the keyword 'SET'.
> Server: Msg 111, Level 15, State 1, Procedure DmView1,
> Line 16
> 'CREATE VIEW' must be the first statement in a query batch.
> Now I have to create views at one go as i create all the
> tables at one go by running the SQL-script through my code.
> ur suggestions are welcome.
> Billi98
>sql
Recency, time since last sale
Hi,
I'm trying to implement a recency measure for my individual customers,
telling me how many days have gone by since the last purchase of a customer.
I would like it to go something like this:
with member time.week.last_purchase_date as
'Tail(Filter([Time].[Week].[Date].members, Not
IsEmpty(([Measures].[Quantity],[Customers].[Geography].CurrentMember)))).Item(0).Item(0).uniquename '
member measures.days_since_last_purchase as
'Datediff(time.week.lastpurchasedate : [Time].[Week].Currentmember)'
Of course there is no Datediff in MDX, but how can I construct the syntax to
meet my requirements?
Many thanks!
have you tried using vba functions? DateDiff() and CDate() ?
"Jacob_I" wrote:
> Hi,
> I'm trying to implement a recency measure for my individual customers,
> telling me how many days have gone by since the last purchase of a customer.
> I would like it to go something like this:
> with member time.week.last_purchase_date as
> 'Tail(Filter([Time].[Week].[Date].members, Not
> IsEmpty(([Measures].[Quantity],[Customers].[Geography].CurrentMember)))).Item(0).Item(0).uniquename '
> member measures.days_since_last_purchase as
> 'Datediff(time.week.lastpurchasedate : [Time].[Week].Currentmember)'
> Of course there is no Datediff in MDX, but how can I construct the syntax to
> meet my requirements?
> Many thanks!
|||Hi Mike
Actually, I didn't think about that at all. I'll try that and post my
findings.
"mike" wrote:
[vbcol=seagreen]
> have you tried using vba functions? DateDiff() and CDate() ?
> "Jacob_I" wrote:
|||As far as the MDX goes, you could substract index positions of two dates.
It would mean that you find index position of last purchase date in the date
dimension and then find index position of 'today' or some other date...
MC
"Jacob_I" <JacobI@.discussions.microsoft.com> wrote in message
news:5C0C8187-C289-4E36-92BE-11F711D5B6E1@.microsoft.com...[vbcol=seagreen]
> Hi Mike
> Actually, I didn't think about that at all. I'll try that and post my
> findings.
> "mike" wrote:
|||Thanks a lot Mike & MC. I've gotten the datediff stuff working beautifully
thansk to you valuable advice. But I also need it to be time-sensitive, so
that when I use the calc member:
'Tail(Filter([Time].[Week].[Date].members, Not
IsEmpty(([Measures].[Quantity],[Customers].[Geography].CurrentMember)))).Item(0).Item(0).uniquename '
...the [Time].[Week].[Date].members is replaced by a set of members that
looks something like ([time].[week].(All):[Time].[week].Currentmember) ie. it
returns all members from beginning of time until time.currentmember.
Can this be done? Maybe it's woth a new thread?
Thanks in advance!
Regards, Jacob
|||In article <E88FB2ED-46C5-4DDC-B4A6-C1222C611986@.microsoft.com>,
JacobI@.discussions.microsoft.com says...
> ..the [Time].[Week].[Date].members is replaced by a set of members that
> looks something like ([time].[week].(All):[Time].[week].Currentmember) ie. it
> returns all members from beginning of time until time.currentmember.
>
You could use something like
[time].[week].members.item(0):[Time].[week].Currentmember
Or, to be completely idependant of which level you are on:
[time].CurrentMember.Level.Members.item(0):[Time].[week].Currentmember
HTH
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell
|||hi Jacob,
I am also facing a similar problem with the datediff. Could you share on how
you overcame the prob on datediff.
Thanks in advance
Prady
"Jacob_I" wrote:
> Thanks a lot Mike & MC. I've gotten the datediff stuff working beautifully
> thansk to you valuable advice. But I also need it to be time-sensitive, so
> that when I use the calc member:
> 'Tail(Filter([Time].[Week].[Date].members, Not
> IsEmpty(([Measures].[Quantity],[Customers].[Geography].CurrentMember)))).Item(0).Item(0).uniquename '
> ..the [Time].[Week].[Date].members is replaced by a set of members that
> looks something like ([time].[week].(All):[Time].[week].Currentmember) ie. it
> returns all members from beginning of time until time.currentmember.
> Can this be done? Maybe it's woth a new thread?
> Thanks in advance!
> Regards, Jacob
>
>
|||Hi Prady,
Although I don't have the code right here, I can illustrate the layout of my
final query:
// This part gives me the date of last puchase and case it to DATE type
CDate(Tail(Filter({<Configure a date member range>}, Not
IsEmpty(([Measures].[Quantity],[Customers].[Geography].CurrentMember)))).Item(0).Item(0).uniquename) -
// Minus the currentdate
Now()
(end)
The date member range can be anything from a date range in a named set to
something that changes with the time.currentmember, eg.
{time.currentmember.lag(182):time.currentmembe r} which if a date-level will
give you a range of half a year. As this query if quite heavy for at large
customer dimension it's rather sensible to have a small date member range.
The minus part can also be Cdate(time.currentmember.name) which (depending
on your data level member formatting) also will give you a DATE type result
to minus with the first part.
HTH
Jacob_I
I'm trying to implement a recency measure for my individual customers,
telling me how many days have gone by since the last purchase of a customer.
I would like it to go something like this:
with member time.week.last_purchase_date as
'Tail(Filter([Time].[Week].[Date].members, Not
IsEmpty(([Measures].[Quantity],[Customers].[Geography].CurrentMember)))).Item(0).Item(0).uniquename '
member measures.days_since_last_purchase as
'Datediff(time.week.lastpurchasedate : [Time].[Week].Currentmember)'
Of course there is no Datediff in MDX, but how can I construct the syntax to
meet my requirements?
Many thanks!
have you tried using vba functions? DateDiff() and CDate() ?
"Jacob_I" wrote:
> Hi,
> I'm trying to implement a recency measure for my individual customers,
> telling me how many days have gone by since the last purchase of a customer.
> I would like it to go something like this:
> with member time.week.last_purchase_date as
> 'Tail(Filter([Time].[Week].[Date].members, Not
> IsEmpty(([Measures].[Quantity],[Customers].[Geography].CurrentMember)))).Item(0).Item(0).uniquename '
> member measures.days_since_last_purchase as
> 'Datediff(time.week.lastpurchasedate : [Time].[Week].Currentmember)'
> Of course there is no Datediff in MDX, but how can I construct the syntax to
> meet my requirements?
> Many thanks!
|||Hi Mike
Actually, I didn't think about that at all. I'll try that and post my
findings.
"mike" wrote:
[vbcol=seagreen]
> have you tried using vba functions? DateDiff() and CDate() ?
> "Jacob_I" wrote:
|||As far as the MDX goes, you could substract index positions of two dates.
It would mean that you find index position of last purchase date in the date
dimension and then find index position of 'today' or some other date...
MC
"Jacob_I" <JacobI@.discussions.microsoft.com> wrote in message
news:5C0C8187-C289-4E36-92BE-11F711D5B6E1@.microsoft.com...[vbcol=seagreen]
> Hi Mike
> Actually, I didn't think about that at all. I'll try that and post my
> findings.
> "mike" wrote:
|||Thanks a lot Mike & MC. I've gotten the datediff stuff working beautifully
thansk to you valuable advice. But I also need it to be time-sensitive, so
that when I use the calc member:
'Tail(Filter([Time].[Week].[Date].members, Not
IsEmpty(([Measures].[Quantity],[Customers].[Geography].CurrentMember)))).Item(0).Item(0).uniquename '
...the [Time].[Week].[Date].members is replaced by a set of members that
looks something like ([time].[week].(All):[Time].[week].Currentmember) ie. it
returns all members from beginning of time until time.currentmember.
Can this be done? Maybe it's woth a new thread?
Thanks in advance!
Regards, Jacob
|||In article <E88FB2ED-46C5-4DDC-B4A6-C1222C611986@.microsoft.com>,
JacobI@.discussions.microsoft.com says...
> ..the [Time].[Week].[Date].members is replaced by a set of members that
> looks something like ([time].[week].(All):[Time].[week].Currentmember) ie. it
> returns all members from beginning of time until time.currentmember.
>
You could use something like
[time].[week].members.item(0):[Time].[week].Currentmember
Or, to be completely idependant of which level you are on:
[time].CurrentMember.Level.Members.item(0):[Time].[week].Currentmember
HTH
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell
|||hi Jacob,
I am also facing a similar problem with the datediff. Could you share on how
you overcame the prob on datediff.
Thanks in advance
Prady
"Jacob_I" wrote:
> Thanks a lot Mike & MC. I've gotten the datediff stuff working beautifully
> thansk to you valuable advice. But I also need it to be time-sensitive, so
> that when I use the calc member:
> 'Tail(Filter([Time].[Week].[Date].members, Not
> IsEmpty(([Measures].[Quantity],[Customers].[Geography].CurrentMember)))).Item(0).Item(0).uniquename '
> ..the [Time].[Week].[Date].members is replaced by a set of members that
> looks something like ([time].[week].(All):[Time].[week].Currentmember) ie. it
> returns all members from beginning of time until time.currentmember.
> Can this be done? Maybe it's woth a new thread?
> Thanks in advance!
> Regards, Jacob
>
>
|||Hi Prady,
Although I don't have the code right here, I can illustrate the layout of my
final query:
// This part gives me the date of last puchase and case it to DATE type
CDate(Tail(Filter({<Configure a date member range>}, Not
IsEmpty(([Measures].[Quantity],[Customers].[Geography].CurrentMember)))).Item(0).Item(0).uniquename) -
// Minus the currentdate
Now()
(end)
The date member range can be anything from a date range in a named set to
something that changes with the time.currentmember, eg.
{time.currentmember.lag(182):time.currentmembe r} which if a date-level will
give you a range of half a year. As this query if quite heavy for at large
customer dimension it's rather sensible to have a small date member range.
The minus part can also be Cdate(time.currentmember.name) which (depending
on your data level member formatting) also will give you a DATE type result
to minus with the first part.
HTH
Jacob_I
Recency, time since last sale
Hi,
I'm trying to implement a recency measure for my individual customers,
telling me how many days have gone by since the last purchase of a customer.
I would like it to go something like this:
with member time.week.last_purchase_date as
'Tail(Filter([Time].[Week].[Date].members, Not
IsEmpty(([Measures].[Quantity],[Customers].[Geography].Curre
ntMember)))).Item(0).Item(0).uniquename '
member measures.days_since_last_purchase as
'Datediff(time.week.lastpurchasedate : [Time].[Week].Currentmember)'
Of course there is no Datediff in MDX, but how can I construct the syntax to
meet my requirements?
Many thanks!have you tried using vba functions? DateDiff() and CDate() '
"Jacob_I" wrote:
> Hi,
> I'm trying to implement a recency measure for my individual customers,
> telling me how many days have gone by since the last purchase of a custome
r.
> I would like it to go something like this:
> with member time.week.last_purchase_date as
> 'Tail(Filter([Time].[Week].[Date].members, Not
> IsEmpty(([Measures].[Quantity],[Customers].[Geography].Cur
rentMember)))).Item(0).Item(0).uniquename '
> member measures.days_since_last_purchase as
> 'Datediff(time.week.lastpurchasedate : [Time].[Week].Currentmember
)'
> Of course there is no Datediff in MDX, but how can I construct the syntax
to
> meet my requirements?
> Many thanks!|||Hi Mike
Actually, I didn't think about that at all. I'll try that and post my
findings.
"mike" wrote:
[vbcol=seagreen]
> have you tried using vba functions? DateDiff() and CDate() '
> "Jacob_I" wrote:
>|||As far as the MDX goes, you could substract index positions of two dates.
It would mean that you find index position of last purchase date in the date
dimension and then find index position of 'today' or some other date...
MC
"Jacob_I" <JacobI@.discussions.microsoft.com> wrote in message
news:5C0C8187-C289-4E36-92BE-11F711D5B6E1@.microsoft.com...[vbcol=seagreen]
> Hi Mike
> Actually, I didn't think about that at all. I'll try that and post my
> findings.
> "mike" wrote:
>|||Thanks a lot Mike & MC. I've gotten the datediff stuff working beautifully
thansk to you valuable advice. But I also need it to be time-sensitive, so
that when I use the calc member:
'Tail(Filter([Time].[Week].[Date].members, Not
IsEmpty(([Measures].[Quantity],[Customers].[Geography].Curre
ntMember)))).Item(0).Item(0).uniquename '
..the [Time].[Week].[Date].members is replaced by a set of memb
ers that
looks something like ([time].[week].(All):[Time].[week].Curr
entmember) ie. it
returns all members from beginning of time until time.currentmember.
Can this be done? Maybe it's woth a new thread?
Thanks in advance!
Regards, Jacob|||In article <E88FB2ED-46C5-4DDC-B4A6-C1222C611986@.microsoft.com>,
JacobI@.discussions.microsoft.com says...
> ..the [Time].[Week].[Date].members is replaced by a set of mem
bers that
> looks something like ([time].[week].(All):[Time].[week].Cu
rrentmember) ie. it
> returns all members from beginning of time until time.currentmember.
>
You could use something like
[time].[week].members.item(0):[Time].[week].Currentmember
Or, to be completely idependant of which level you are on:
[time].CurrentMember.Level.Members.item(0):[Time].[week].Current
member
HTH
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell|||hi Jacob,
I am also facing a similar problem with the datediff. Could you share on how
you overcame the prob on datediff.
Thanks in advance
Prady
"Jacob_I" wrote:
> Thanks a lot Mike & MC. I've gotten the datediff stuff working beautifully
> thansk to you valuable advice. But I also need it to be time-sensitive, so
> that when I use the calc member:
> 'Tail(Filter([Time].[Week].[Date].members, Not
> IsEmpty(([Measures].[Quantity],[Customers].[Geography].Cur
rentMember)))).Item(0).Item(0).uniquename '
> ..the [Time].[Week].[Date].members is replaced by a set of mem
bers that
> looks something like ([time].[week].(All):[Time].[week].Cu
rrentmember) ie. it
> returns all members from beginning of time until time.currentmember.
> Can this be done? Maybe it's woth a new thread?
> Thanks in advance!
> Regards, Jacob
>
>|||Hi Prady,
Although I don't have the code right here, I can illustrate the layout of my
final query:
// This part gives me the date of last puchase and case it to DATE type
CDate(Tail(Filter({<Configure a date member range>}, Not
IsEmpty(([Measures].[Quantity],[Customers].[Geography].Curre
ntMember)))).Item(0).Item(0).uniquename) -
// Minus the currentdate
Now()
(end)
The date member range can be anything from a date range in a named set to
something that changes with the time.currentmember, eg.
{time.currentmember.lag(182):time.currentmember} which if a date-level
will
give you a range of half a year. As this query if quite heavy for at large
customer dimension it's rather sensible to have a small date member range.
The minus part can also be Cdate(time.currentmember.name) which (depending
on your data level member formatting) also will give you a DATE type result
to minus with the first part.
HTH
Jacob_I
I'm trying to implement a recency measure for my individual customers,
telling me how many days have gone by since the last purchase of a customer.
I would like it to go something like this:
with member time.week.last_purchase_date as
'Tail(Filter([Time].[Week].[Date].members, Not
IsEmpty(([Measures].[Quantity],[Customers].[Geography].Curre
ntMember)))).Item(0).Item(0).uniquename '
member measures.days_since_last_purchase as
'Datediff(time.week.lastpurchasedate : [Time].[Week].Currentmember)'
Of course there is no Datediff in MDX, but how can I construct the syntax to
meet my requirements?
Many thanks!have you tried using vba functions? DateDiff() and CDate() '
"Jacob_I" wrote:
> Hi,
> I'm trying to implement a recency measure for my individual customers,
> telling me how many days have gone by since the last purchase of a custome
r.
> I would like it to go something like this:
> with member time.week.last_purchase_date as
> 'Tail(Filter([Time].[Week].[Date].members, Not
> IsEmpty(([Measures].[Quantity],[Customers].[Geography].Cur
rentMember)))).Item(0).Item(0).uniquename '
> member measures.days_since_last_purchase as
> 'Datediff(time.week.lastpurchasedate : [Time].[Week].Currentmember
)'
> Of course there is no Datediff in MDX, but how can I construct the syntax
to
> meet my requirements?
> Many thanks!|||Hi Mike
Actually, I didn't think about that at all. I'll try that and post my
findings.
"mike" wrote:
[vbcol=seagreen]
> have you tried using vba functions? DateDiff() and CDate() '
> "Jacob_I" wrote:
>|||As far as the MDX goes, you could substract index positions of two dates.
It would mean that you find index position of last purchase date in the date
dimension and then find index position of 'today' or some other date...
MC
"Jacob_I" <JacobI@.discussions.microsoft.com> wrote in message
news:5C0C8187-C289-4E36-92BE-11F711D5B6E1@.microsoft.com...[vbcol=seagreen]
> Hi Mike
> Actually, I didn't think about that at all. I'll try that and post my
> findings.
> "mike" wrote:
>|||Thanks a lot Mike & MC. I've gotten the datediff stuff working beautifully
thansk to you valuable advice. But I also need it to be time-sensitive, so
that when I use the calc member:
'Tail(Filter([Time].[Week].[Date].members, Not
IsEmpty(([Measures].[Quantity],[Customers].[Geography].Curre
ntMember)))).Item(0).Item(0).uniquename '
..the [Time].[Week].[Date].members is replaced by a set of memb
ers that
looks something like ([time].[week].(All):[Time].[week].Curr
entmember) ie. it
returns all members from beginning of time until time.currentmember.
Can this be done? Maybe it's woth a new thread?
Thanks in advance!
Regards, Jacob|||In article <E88FB2ED-46C5-4DDC-B4A6-C1222C611986@.microsoft.com>,
JacobI@.discussions.microsoft.com says...
> ..the [Time].[Week].[Date].members is replaced by a set of mem
bers that
> looks something like ([time].[week].(All):[Time].[week].Cu
rrentmember) ie. it
> returns all members from beginning of time until time.currentmember.
>
You could use something like
[time].[week].members.item(0):[Time].[week].Currentmember
Or, to be completely idependant of which level you are on:
[time].CurrentMember.Level.Members.item(0):[Time].[week].Current
member
HTH
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell|||hi Jacob,
I am also facing a similar problem with the datediff. Could you share on how
you overcame the prob on datediff.
Thanks in advance
Prady
"Jacob_I" wrote:
> Thanks a lot Mike & MC. I've gotten the datediff stuff working beautifully
> thansk to you valuable advice. But I also need it to be time-sensitive, so
> that when I use the calc member:
> 'Tail(Filter([Time].[Week].[Date].members, Not
> IsEmpty(([Measures].[Quantity],[Customers].[Geography].Cur
rentMember)))).Item(0).Item(0).uniquename '
> ..the [Time].[Week].[Date].members is replaced by a set of mem
bers that
> looks something like ([time].[week].(All):[Time].[week].Cu
rrentmember) ie. it
> returns all members from beginning of time until time.currentmember.
> Can this be done? Maybe it's woth a new thread?
> Thanks in advance!
> Regards, Jacob
>
>|||Hi Prady,
Although I don't have the code right here, I can illustrate the layout of my
final query:
// This part gives me the date of last puchase and case it to DATE type
CDate(Tail(Filter({<Configure a date member range>}, Not
IsEmpty(([Measures].[Quantity],[Customers].[Geography].Curre
ntMember)))).Item(0).Item(0).uniquename) -
// Minus the currentdate
Now()
(end)
The date member range can be anything from a date range in a named set to
something that changes with the time.currentmember, eg.
{time.currentmember.lag(182):time.currentmember} which if a date-level
will
give you a range of half a year. As this query if quite heavy for at large
customer dimension it's rather sensible to have a small date member range.
The minus part can also be Cdate(time.currentmember.name) which (depending
on your data level member formatting) also will give you a DATE type result
to minus with the first part.
HTH
Jacob_I
Receiving this error since migrating to SQL 2000 from SQL 7
Three simple suggestions:
1- Run the DTS package manually and see where (Which step)
you get the error.
2- Create an output file through Package-->Properties--
>Logging in the DTS package and read the output file for
the error.
3- If you upgraded from SQL Server 7.0 to 2000, run
sp_updatestats stored proc for all the databases in the QA.
>--Original Message--
>Ever since migrating to SQL 2000 from SQL 7 I receive
this error at least
>once a day while running jobs through SQL Agent. It may
not be the same job
>having the problem. Any thoughts?
>Executed as user: domain\user. DTSRun: Loading...
Error: -2147467259
>(80004005); Provider Error: 0 (0) Error string:
Timeout expired
>Error source: Microsoft OLE DB Provider for SQL
Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.
>.
>
The job is only failing once or twice a day even though it runs every hour or
in the case of another job, every 1/2 hour. It is never the same time of
day. I can run the DTS job manually and it work without failing. I will
give the logging a try and the sp_updatestats. I didn't upgrade the server -
it was a clean install and a restore from SQL 7. Thanks for your help
"Mark" wrote:
> Three simple suggestions:
> 1- Run the DTS package manually and see where (Which step)
> you get the error.
> 2- Create an output file through Package-->Properties--
> the error.
> 3- If you upgraded from SQL Server 7.0 to 2000, run
> sp_updatestats stored proc for all the databases in the QA.
>
>
> this error at least
> not be the same job
> Error: -2147467259
> Timeout expired
> Server Help file:
>
1- Run the DTS package manually and see where (Which step)
you get the error.
2- Create an output file through Package-->Properties--
>Logging in the DTS package and read the output file for
the error.
3- If you upgraded from SQL Server 7.0 to 2000, run
sp_updatestats stored proc for all the databases in the QA.
>--Original Message--
>Ever since migrating to SQL 2000 from SQL 7 I receive
this error at least
>once a day while running jobs through SQL Agent. It may
not be the same job
>having the problem. Any thoughts?
>Executed as user: domain\user. DTSRun: Loading...
Error: -2147467259
>(80004005); Provider Error: 0 (0) Error string:
Timeout expired
>Error source: Microsoft OLE DB Provider for SQL
Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.
>.
>
The job is only failing once or twice a day even though it runs every hour or
in the case of another job, every 1/2 hour. It is never the same time of
day. I can run the DTS job manually and it work without failing. I will
give the logging a try and the sp_updatestats. I didn't upgrade the server -
it was a clean install and a restore from SQL 7. Thanks for your help
"Mark" wrote:
> Three simple suggestions:
> 1- Run the DTS package manually and see where (Which step)
> you get the error.
> 2- Create an output file through Package-->Properties--
> the error.
> 3- If you upgraded from SQL Server 7.0 to 2000, run
> sp_updatestats stored proc for all the databases in the QA.
>
>
> this error at least
> not be the same job
> Error: -2147467259
> Timeout expired
> Server Help file:
>
Receiving this error since migrating to SQL 2000 from SQL 7
Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
once a day while running jobs through SQL Agent. It may not be the same job
having the problem. Any thoughts?
Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
(80004005); Provider Error: 0 (0) Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL Server Help file:
Help context: 0. Process Exit Code 1. The step failed.
I have ran the jobs numerous times with DTS and they do not fail. I have run
the sp_updatestats on all databases on this server and I have turned on
logging with DTS and this job does not log anything when I get the timeout
message. Thanks for any other advice you can give. My customer is getting
very frustrated that this keeps not running.
"Connie" wrote:
> Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
> once a day while running jobs through SQL Agent. It may not be the same job
> having the problem. Any thoughts?
> Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
> (80004005); Provider Error: 0 (0) Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.
once a day while running jobs through SQL Agent. It may not be the same job
having the problem. Any thoughts?
Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
(80004005); Provider Error: 0 (0) Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL Server Help file:
Help context: 0. Process Exit Code 1. The step failed.
I have ran the jobs numerous times with DTS and they do not fail. I have run
the sp_updatestats on all databases on this server and I have turned on
logging with DTS and this job does not log anything when I get the timeout
message. Thanks for any other advice you can give. My customer is getting
very frustrated that this keeps not running.
"Connie" wrote:
> Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
> once a day while running jobs through SQL Agent. It may not be the same job
> having the problem. Any thoughts?
> Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
> (80004005); Provider Error: 0 (0) Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.
Receiving this error since migrating to SQL 2000 from SQL 7
Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
once a day while running jobs through SQL Agent. It may not be the same job
having the problem. Any thoughts?
Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
(80004005); Provider Error: 0 (0) Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL Server Help file:
Help context: 0. Process Exit Code 1. The step failed.Three simple suggestions:
1- Run the DTS package manually and see where (Which step)
you get the error.
2- Create an output file through Package-->Properties--
>Logging in the DTS package and read the output file for
the error.
3- If you upgraded from SQL Server 7.0 to 2000, run
sp_updatestats stored proc for all the databases in the QA.
>--Original Message--
>Ever since migrating to SQL 2000 from SQL 7 I receive
this error at least
>once a day while running jobs through SQL Agent. It may
not be the same job
>having the problem. Any thoughts?
>Executed as user: domain\user. DTSRun: Loading...
Error: -2147467259
>(80004005); Provider Error: 0 (0) Error string:
Timeout expired
>Error source: Microsoft OLE DB Provider for SQL
Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.
>.
>|||The job is only failing once or twice a day even though it runs every hour or
in the case of another job, every 1/2 hour. It is never the same time of
day. I can run the DTS job manually and it work without failing. I will
give the logging a try and the sp_updatestats. I didn't upgrade the server -
it was a clean install and a restore from SQL 7. Thanks for your help
"Mark" wrote:
> Three simple suggestions:
> 1- Run the DTS package manually and see where (Which step)
> you get the error.
> 2- Create an output file through Package-->Properties--
> >Logging in the DTS package and read the output file for
> the error.
> 3- If you upgraded from SQL Server 7.0 to 2000, run
> sp_updatestats stored proc for all the databases in the QA.
>
>
> >--Original Message--
> >Ever since migrating to SQL 2000 from SQL 7 I receive
> this error at least
> >once a day while running jobs through SQL Agent. It may
> not be the same job
> >having the problem. Any thoughts?
> >
> >Executed as user: domain\user. DTSRun: Loading...
> Error: -2147467259
> >(80004005); Provider Error: 0 (0) Error string:
> Timeout expired
> >Error source: Microsoft OLE DB Provider for SQL
> Server Help file:
> > Help context: 0. Process Exit Code 1. The step failed.
> >.
> >
>|||I have ran the jobs numerous times with DTS and they do not fail. I have run
the sp_updatestats on all databases on this server and I have turned on
logging with DTS and this job does not log anything when I get the timeout
message. Thanks for any other advice you can give. My customer is getting
very frustrated that this keeps not running.
"Connie" wrote:
> Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
> once a day while running jobs through SQL Agent. It may not be the same job
> having the problem. Any thoughts?
> Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
> (80004005); Provider Error: 0 (0) Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.sql
once a day while running jobs through SQL Agent. It may not be the same job
having the problem. Any thoughts?
Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
(80004005); Provider Error: 0 (0) Error string: Timeout expired
Error source: Microsoft OLE DB Provider for SQL Server Help file:
Help context: 0. Process Exit Code 1. The step failed.Three simple suggestions:
1- Run the DTS package manually and see where (Which step)
you get the error.
2- Create an output file through Package-->Properties--
>Logging in the DTS package and read the output file for
the error.
3- If you upgraded from SQL Server 7.0 to 2000, run
sp_updatestats stored proc for all the databases in the QA.
>--Original Message--
>Ever since migrating to SQL 2000 from SQL 7 I receive
this error at least
>once a day while running jobs through SQL Agent. It may
not be the same job
>having the problem. Any thoughts?
>Executed as user: domain\user. DTSRun: Loading...
Error: -2147467259
>(80004005); Provider Error: 0 (0) Error string:
Timeout expired
>Error source: Microsoft OLE DB Provider for SQL
Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.
>.
>|||The job is only failing once or twice a day even though it runs every hour or
in the case of another job, every 1/2 hour. It is never the same time of
day. I can run the DTS job manually and it work without failing. I will
give the logging a try and the sp_updatestats. I didn't upgrade the server -
it was a clean install and a restore from SQL 7. Thanks for your help
"Mark" wrote:
> Three simple suggestions:
> 1- Run the DTS package manually and see where (Which step)
> you get the error.
> 2- Create an output file through Package-->Properties--
> >Logging in the DTS package and read the output file for
> the error.
> 3- If you upgraded from SQL Server 7.0 to 2000, run
> sp_updatestats stored proc for all the databases in the QA.
>
>
> >--Original Message--
> >Ever since migrating to SQL 2000 from SQL 7 I receive
> this error at least
> >once a day while running jobs through SQL Agent. It may
> not be the same job
> >having the problem. Any thoughts?
> >
> >Executed as user: domain\user. DTSRun: Loading...
> Error: -2147467259
> >(80004005); Provider Error: 0 (0) Error string:
> Timeout expired
> >Error source: Microsoft OLE DB Provider for SQL
> Server Help file:
> > Help context: 0. Process Exit Code 1. The step failed.
> >.
> >
>|||I have ran the jobs numerous times with DTS and they do not fail. I have run
the sp_updatestats on all databases on this server and I have turned on
logging with DTS and this job does not log anything when I get the timeout
message. Thanks for any other advice you can give. My customer is getting
very frustrated that this keeps not running.
"Connie" wrote:
> Ever since migrating to SQL 2000 from SQL 7 I receive this error at least
> once a day while running jobs through SQL Agent. It may not be the same job
> having the problem. Any thoughts?
> Executed as user: domain\user. DTSRun: Loading... Error: -2147467259
> (80004005); Provider Error: 0 (0) Error string: Timeout expired
> Error source: Microsoft OLE DB Provider for SQL Server Help file:
> Help context: 0. Process Exit Code 1. The step failed.sql
Receiving system error when retrieving database record with null value
I have some VB.NET code to retrieve data from an SQL Server database and display it. The code is as follows:
-------------------------------sw_calendar = calendarAdapter.GetEventByID(cid)
If sw_calendar.Rows.Count > 0Then
lblStartDateText.Text = sw_calendar(0).eventStartDate
lblEndDateText.Text = sw_calendar(0).eventEndDate
lblTitleText.Text = sw_calendar(0).title
lblLocationText.Text = sw_calendar(0).location
lblDescriptionText.Text = sw_calendar(0).description
Else
lblStartDateText.Text ="*** Not Found ***"
lblEndDateText.Text ="*** Not Found ***"
lblTitleText.Text ="*** Not Found ***"
lblLocationText.Text ="*** Not Found ***"
lblDescriptionText.Text ="*** Not Found ***"
EndIf
-------------------------------
If all of the fields in the database has values, everything works ok. However, if the title, location or description fields have a null value, I receive the following error message:
Unable to cast object of type 'System.DBNull' to type 'System.String'.
I've tried a bunch of different things such as:
Adding ".ToString" to the database field,Seeing if the value is null: If sw_calendar(0).description = system.DBnull.value......but either I get syntax errors in the code, or if the syntax is ok, I still get the above error message.
Can anyone help me with the code required to trap the nullwithin the code example I've provided? I'm sure there are other, and better, ways to code this, but for now I'd really like to get it working as is, and then optimize the code once the application is working (...can you tell I have a tight deadline
)
Thanks,
Brad
Check forDBNullin VB.NET, with optional specification of type, so itconverts null to the appropriate value (e.g., "" for string, 0 fornumbers).
Good luck.
|||Something like:
sw_calendar = calendarAdapter.GetEventByID(cid)If sw_calendar.Rows.Count > 0Then IF NOT IsDBNull(sw_calendar(0).eventStartDate)Then lblStartDateText.Text = sw_calendar(0).eventStartDate ELSEblStartDateText.Text ="*** Not Found ***" END IF IF NOT IsDBNull(sw_calendar(0).eventEndDate)Then lblEndDateText.Text = sw_calendar(0).eventEndDate ELSE lblEndDateText.Text ="*** Not Found ***" END IF IF NOT IsDBNull(sw_calendar(0).title) THEN lblTitleText.Text = sw_calendar(0).title ELSE lblTitleText.Text ="*** Not Found ***" END IF IF NOT IsDBNull(sw_calendar(0).location) THEN lblLocationText.Text = sw_calendar(0).location ELSE lblLocationText.Text ="*** Not Found ***" END IF IF NOT IsDBNull(sw_calendar(0).description) THEN lblDescriptionText.Text = sw_calendar(0).description ELSE lblDescriptionText.Text ="*** Not Found ***" END IFGood luck.|||
Hi,
I tried addingIF NOT IsDBNull... but I still get the same error message. To make sure the problem is what I think it is, I changed the value of the description field in the database to a single space. After doing this, page renders fine. When I delete the space, the error returns. So, there is still a problem evaluating sw_calendar(0).location within the IsDBNull function.
Any ideas?
|||
I just tried:
If sw_calendar(0).description.Length >= 1Then
lblDescriptionText.Text = sw_calendar(0).description
Else
lblDescriptionText.Text =" "
EndIf
and itstill generates theUnable to cast object of type 'System.DBNull' to type 'System.String'. error message!
|||The problem isnt with IsDbNull. The problem is with the strongly typed data row you are using. If you try to do IsDbNull(sw_calendar(0).description), sw_calendar tries to convert the description to a string and then pass that value to IsDBNull. However, sincesw_calendar(0).description is DBNull, it will always throw this error before DbNull ever gets it.
This, in my opinion, has crippled the Strongly Typed DataSets that are created with the TableAdapters.
The workaround is not to try to get the description withsw_calendar(0).description. Instead, usesw_calendar(0)("description"). Its not strongly typed, but at least it wont crash your app.
One option would be to convert the values of NULLs to '' in case of strings and 0 or something similar in case of integers. You can achieve this in your query itself. There is a function call ISNULL in SQL. Basically you can use this function like ISNULL ( <column name> , '' ). This will replace the null values in the column to '' ( blank which is a legal string BLOCKED EXPRESSION. You can write select isnull ( description , '' ) as description. Then you are rest assured that the query itself will give you the valid string values instead of null and you having to bother to convert those nulls to blank string or something similar.
You can use this type of query when you are not sured about the values contained in the column, I mean in case the column may contain nulls also.
Hope this will help.
Subscribe to:
Posts (Atom)