If client is synchronizing for first time with server at that time
Snapshot is applied to the client database. If meanwhile application
crashes or network goes down then snapshot is partially applied. When
i am restarting my application and trying to synchronize again my
server database gets corrupted (i.e. some rows get deleted from
central server)
So when a new subsciber is synchronising for first time and meanwhile
the process crashes then what will happen and how to resolve it.
On Nov 15, 12:07 pm, Manish <jainmani...@.gmail.com> wrote:
> If client is synchronizing for first time with server at that time
> Snapshot is applied to the client database. If meanwhile application
> crashes or network goes down then snapshot is partially applied. When
> i am restarting my application and trying to synchronize again my
> server database gets corrupted (i.e. some rows get deleted from
> central server)
> So when a new subsciber is synchronising for first time and meanwhile
> the process crashes then what will happen and how to resolve it.
Currently I done following and problem disappeared. But pls suggest
other options.
When i observed replication related system tables i decided to kill
processed to related to
string sql = "select spid from master.dbo.sysprocesses WHERE
program_name like '" + getMergeAgentProgramName() + "%'"; where
getMergeAgentProgramName() is as follows
private string getMergeAgentProgramName()
{
return mPublisher + "-" +
mPublicationDatabase + "-" +
mPublication + "-" +
mSubscriber;
}
the query will get processes related to replication
after that i killed each process selected under above sql query.
foreach (string spid in spIds)
{
sql = "kill " + spid;
publisherConn.ExecuteNonQuery(sql);
}
but the solution seems un scalable and may be unreliable.
Showing posts with label applied. Show all posts
Showing posts with label applied. Show all posts
Tuesday, March 20, 2012
Applying SP4. Do you have to provide sa password?
I have never applied a service pack to sql server 2000. Someone tells me that you have an option of supplying the SA password but do not have to and the service pack is applied just as if you did supply the SA password. This sounds odd to me. So, is it true? I am asking because our server instance shows "SP4" but a fix that was supposed to be included in SP4 was apparently not as the problem persists (link from sql server 2005 to 2000 fails when referenced in sql2005). I was thinking that whoever ran the service pack may not have provided the SA password so some of the SP4 was not applied?
Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO" for OLE DB provider "SQLNCLI" for linked server "s-1". The provider supports the interface, but returns a failure code when it is used.
Thanks.
The service pack ask for the password, It allows to continue without a password, and it provides a notice about the dangers of so doing.
So yes, the service pack may have been properly applied without a password -IF the sa account did not have a password.
|||There are two ways to log into a SQL Server. One is by specifing a login and password, such as the "sa" login. The other is by using the Windows Creditentials which the user has logged into the operating system with. When installing the service pack you have the option of logging in with which ever method you would like to; either the "sa" account or the Windows account.
What command is being performed when this error comes up?
|||The above errors arise when trying to issue a select statement on the 2005 server which references tables on the 2000 server which it is linked to. I thought perhaps the person who applied the service pack 4 may not have done it correctly. I was not there, and have never done it myself. The message may imply missing components.
ex. On 2005 server: Select * From linked2000server.mydb.dbo.mytable
|||Can you query any tables over the linked server, or is this one the only one causing the problem?
If it's every table a sp4 reinstall may be in order on the SQL 2000 server.
|||Nope!Applying SP4. Do you have to provide sa password?
I have never applied a service pack to sql server 2000. Someone tells me that you have an option of supplying the SA password but do not have to and the service pack is applied just as if you did supply the SA password. This sounds odd to me. So, is it true? I am asking because our server instance shows "SP4" but a fix that was supposed to be included in SP4 was apparently not as the problem persists (link from sql server 2005 to 2000 fails when referenced in sql2005). I was thinking that whoever ran the service pack may not have provided the SA password so some of the SP4 was not applied?
Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO" for OLE DB provider "SQLNCLI" for linked server "s-1". The provider supports the interface, but returns a failure code when it is used.
Thanks.
The service pack ask for the password, It allows to continue without a password, and it provides a notice about the dangers of so doing.
So yes, the service pack may have been properly applied without a password -IF the sa account did not have a password.
|||There are two ways to log into a SQL Server. One is by specifing a login and password, such as the "sa" login. The other is by using the Windows Creditentials which the user has logged into the operating system with. When installing the service pack you have the option of logging in with which ever method you would like to; either the "sa" account or the Windows account.
What command is being performed when this error comes up?
|||The above errors arise when trying to issue a select statement on the 2005 server which references tables on the 2000 server which it is linked to. I thought perhaps the person who applied the service pack 4 may not have done it correctly. I was not there, and have never done it myself. The message may imply missing components.
ex. On 2005 server: Select * From linked2000server.mydb.dbo.mytable
|||Can you query any tables over the linked server, or is this one the only one causing the problem?
If it's every table a sp4 reinstall may be in order on the SQL 2000 server.
|||Nope!sqlMonday, March 19, 2012
Applying sp4 advice on a server with sql and analysis services
Can anyone tell me if sp4 for analysis services and SQL server 2000 should be
applied together, one before the other, not at all?
--Hi Burt
It is usually better to keep everything in step, and I would apply the
engine first.
John
"burt_king" wrote:
> Can anyone tell me if sp4 for analysis services and SQL server 2000 should be
> applied together, one before the other, not at all?
> --
>|||You can apply them in any order. With SP1 you would need to apply them
together IIRC.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"burt_king" <burt_king@.yahoo.com> wrote in message
news:96F2A6C3-00AA-4BC3-A49D-0294B9B8CC60@.microsoft.com...
> Can anyone tell me if sp4 for analysis services and SQL server 2000 should
> be
> applied together, one before the other, not at all?
> --
>
applied together, one before the other, not at all?
--Hi Burt
It is usually better to keep everything in step, and I would apply the
engine first.
John
"burt_king" wrote:
> Can anyone tell me if sp4 for analysis services and SQL server 2000 should be
> applied together, one before the other, not at all?
> --
>|||You can apply them in any order. With SP1 you would need to apply them
together IIRC.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"burt_king" <burt_king@.yahoo.com> wrote in message
news:96F2A6C3-00AA-4BC3-A49D-0294B9B8CC60@.microsoft.com...
> Can anyone tell me if sp4 for analysis services and SQL server 2000 should
> be
> applied together, one before the other, not at all?
> --
>
applying snapshot
i want to prevent some referential integrity scripts to be deployed at the
subscriber *before* the snapshot is applied , is there a way to interfere
with initial snapshot programmatically?
thanks in advance
There are a couple of ways. You can use the Pre- and Post snapshot commands
to run extra scripts eitehr before or after (or both). You can stop the
distribution task and hand-edit the snapshot after it is created. Note that
the second method will have to be redone on every new snapshot.
As for Referential Integrity, they are not automatically applied since you
may choose to replicate child tables without the parent tables. You can add
them on, but it is not recommended since they tend to interfere with
snapshot application.
Geoff N. Hiten
Microsoft SQL Server MVP
"uykusuz" <yb> wrote in message
news:ewKbjm9gFHA.3568@.TK2MSFTNGP10.phx.gbl...
>i want to prevent some referential integrity scripts to be deployed at the
> subscriber *before* the snapshot is applied , is there a way to
> interfere
> with initial snapshot programmatically?
>
> thanks in advance
>
subscriber *before* the snapshot is applied , is there a way to interfere
with initial snapshot programmatically?
thanks in advance
There are a couple of ways. You can use the Pre- and Post snapshot commands
to run extra scripts eitehr before or after (or both). You can stop the
distribution task and hand-edit the snapshot after it is created. Note that
the second method will have to be redone on every new snapshot.
As for Referential Integrity, they are not automatically applied since you
may choose to replicate child tables without the parent tables. You can add
them on, but it is not recommended since they tend to interfere with
snapshot application.
Geoff N. Hiten
Microsoft SQL Server MVP
"uykusuz" <yb> wrote in message
news:ewKbjm9gFHA.3568@.TK2MSFTNGP10.phx.gbl...
>i want to prevent some referential integrity scripts to be deployed at the
> subscriber *before* the snapshot is applied , is there a way to
> interfere
> with initial snapshot programmatically?
>
> thanks in advance
>
Applying Service Packs
When applying service packs to SQL Server (2000 or 2005), does the service
pack need to be applied to the client tools running on indivdual PCs/Laptops
as well? Thanks.
Hello,
May not be required to all desktops. You can install the service packs to
the desktop machines when ever there is a requirement araise.
Thanks
Hari
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.
|||Please remember that DTS, as an example, is a client tool. If you have
different version of the client on your workstation and your server you run
the risk of getting totally different DTS packages and therefore results.
In SQL2005 the maintenance plans have changed dramatically between SP1 and
SP2. You cannot administer an SP2 created plan with an SP1 client. If a plan
is created on an SP2 server then you would not be able to maintain it from
an SP1 client.
Our rule is to update the client software when the client accesses an
updated server.
Chris
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.
pack need to be applied to the client tools running on indivdual PCs/Laptops
as well? Thanks.
Hello,
May not be required to all desktops. You can install the service packs to
the desktop machines when ever there is a requirement araise.
Thanks
Hari
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.
|||Please remember that DTS, as an example, is a client tool. If you have
different version of the client on your workstation and your server you run
the risk of getting totally different DTS packages and therefore results.
In SQL2005 the maintenance plans have changed dramatically between SP1 and
SP2. You cannot administer an SP2 created plan with an SP1 client. If a plan
is created on an SP2 server then you would not be able to maintain it from
an SP1 client.
Our rule is to update the client software when the client accesses an
updated server.
Chris
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.
Applying Service Packs
When applying service packs to SQL Server (2000 or 2005), does the service
pack need to be applied to the client tools running on indivdual PCs/Laptops
as well? Thanks.Hello,
May not be required to all desktops. You can install the service packs to
the desktop machines when ever there is a requirement araise.
Thanks
Hari
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.|||Hari Prasad wrote:
> Hello,
> May not be required to all desktops. You can install the service packs to
> the desktop machines when ever there is a requirement araise.
> Thanks
> Hari
> "MACason" <MACason@.discussions.microsoft.com> wrote in message
> news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
>
If you are running SQL2000 Analysis Services and upgrade to AS SP4,
you'll have to upgrade your AS Analysis Manager and client tools to SP 4
as well. If you don't do it, you'll get some strange errors when you try
to connect with the client tools. I'm not aware of any other scenarios
where it causes problems to run a lower SP level on the client, but
there might be...;-).
--
Regards
Steen Schlter Persson
Database Administrator / System Administrator|||Please remember that DTS, as an example, is a client tool. If you have
different version of the client on your workstation and your server you run
the risk of getting totally different DTS packages and therefore results.
In SQL2005 the maintenance plans have changed dramatically between SP1 and
SP2. You cannot administer an SP2 created plan with an SP1 client. If a plan
is created on an SP2 server then you would not be able to maintain it from
an SP1 client.
Our rule is to update the client software when the client accesses an
updated server.
Chris
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.
pack need to be applied to the client tools running on indivdual PCs/Laptops
as well? Thanks.Hello,
May not be required to all desktops. You can install the service packs to
the desktop machines when ever there is a requirement araise.
Thanks
Hari
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.|||Hari Prasad wrote:
> Hello,
> May not be required to all desktops. You can install the service packs to
> the desktop machines when ever there is a requirement araise.
> Thanks
> Hari
> "MACason" <MACason@.discussions.microsoft.com> wrote in message
> news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
>
If you are running SQL2000 Analysis Services and upgrade to AS SP4,
you'll have to upgrade your AS Analysis Manager and client tools to SP 4
as well. If you don't do it, you'll get some strange errors when you try
to connect with the client tools. I'm not aware of any other scenarios
where it causes problems to run a lower SP level on the client, but
there might be...;-).
--
Regards
Steen Schlter Persson
Database Administrator / System Administrator|||Please remember that DTS, as an example, is a client tool. If you have
different version of the client on your workstation and your server you run
the risk of getting totally different DTS packages and therefore results.
In SQL2005 the maintenance plans have changed dramatically between SP1 and
SP2. You cannot administer an SP2 created plan with an SP1 client. If a plan
is created on an SP2 server then you would not be able to maintain it from
an SP1 client.
Our rule is to update the client software when the client accesses an
updated server.
Chris
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.
Applying Service Packs
When applying service packs to SQL Server (2000 or 2005), does the service
pack need to be applied to the client tools running on indivdual PCs/Laptops
as well? Thanks.Hello,
May not be required to all desktops. You can install the service packs to
the desktop machines when ever there is a requirement araise.
Thanks
Hari
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.|||Hari Prasad wrote:
> Hello,
> May not be required to all desktops. You can install the service packs to
> the desktop machines when ever there is a requirement araise.
> Thanks
> Hari
> "MACason" <MACason@.discussions.microsoft.com> wrote in message
> news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
>> When applying service packs to SQL Server (2000 or 2005), does the service
>> pack need to be applied to the client tools running on indivdual
>> PCs/Laptops
>> as well? Thanks.
>
If you are running SQL2000 Analysis Services and upgrade to AS SP4,
you'll have to upgrade your AS Analysis Manager and client tools to SP 4
as well. If you don't do it, you'll get some strange errors when you try
to connect with the client tools. I'm not aware of any other scenarios
where it causes problems to run a lower SP level on the client, but
there might be...;-).
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator|||Please remember that DTS, as an example, is a client tool. If you have
different version of the client on your workstation and your server you run
the risk of getting totally different DTS packages and therefore results.
In SQL2005 the maintenance plans have changed dramatically between SP1 and
SP2. You cannot administer an SP2 created plan with an SP1 client. If a plan
is created on an SP2 server then you would not be able to maintain it from
an SP1 client.
Our rule is to update the client software when the client accesses an
updated server.
Chris
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.
pack need to be applied to the client tools running on indivdual PCs/Laptops
as well? Thanks.Hello,
May not be required to all desktops. You can install the service packs to
the desktop machines when ever there is a requirement araise.
Thanks
Hari
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.|||Hari Prasad wrote:
> Hello,
> May not be required to all desktops. You can install the service packs to
> the desktop machines when ever there is a requirement araise.
> Thanks
> Hari
> "MACason" <MACason@.discussions.microsoft.com> wrote in message
> news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
>> When applying service packs to SQL Server (2000 or 2005), does the service
>> pack need to be applied to the client tools running on indivdual
>> PCs/Laptops
>> as well? Thanks.
>
If you are running SQL2000 Analysis Services and upgrade to AS SP4,
you'll have to upgrade your AS Analysis Manager and client tools to SP 4
as well. If you don't do it, you'll get some strange errors when you try
to connect with the client tools. I'm not aware of any other scenarios
where it causes problems to run a lower SP level on the client, but
there might be...;-).
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator|||Please remember that DTS, as an example, is a client tool. If you have
different version of the client on your workstation and your server you run
the risk of getting totally different DTS packages and therefore results.
In SQL2005 the maintenance plans have changed dramatically between SP1 and
SP2. You cannot administer an SP2 created plan with an SP1 client. If a plan
is created on an SP2 server then you would not be able to maintain it from
an SP1 client.
Our rule is to update the client software when the client accesses an
updated server.
Chris
"MACason" <MACason@.discussions.microsoft.com> wrote in message
news:1774B40F-32F8-4A01-8E4B-4C1C381FBE25@.microsoft.com...
> When applying service packs to SQL Server (2000 or 2005), does the service
> pack need to be applied to the client tools running on indivdual
> PCs/Laptops
> as well? Thanks.
Applying MS05-003 broke something...
Hi folks. I have a customer who applied MS05-003 (KB871259) to their server
running MS SQLServer 2000 SP3. On doing this, certain data uploads began to
fail. Once this patch was removed, things began working again. Is there a
known issue with this patch? Has anyone else run across a similar issue? If
so, can someone suggest a work-around or other solution?
Thank you.
Daniel.Please confirm the patch you have installed/un-installed.
MS05-003 is not KB871259
http://www.microsoft.com/technet/se...n/MS05-003.mspx
is 871250.
This patch affect the Indexing Service and replaces the following file on
Win2k
Ciodm.dll
5.0.2195.6981
05-Nov-2004
04:41
68,880
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
My bad. I typoed. The patch applied is MS05-003 / 871250.
Suggestions or known issues?
Daniel.
"Kevin McDonnell [MSFT]" wrote:
> Please confirm the patch you have installed/un-installed.
> MS05-003 is not KB871259
> http://www.microsoft.com/technet/se...n/MS05-003.mspx
> is 871250.
> This patch affect the Indexing Service and replaces the following file on
> Win2k
> Ciodm.dll
> 5.0.2195.6981
> 05-Nov-2004
> 04:41
> 68,880
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||I'm not aware of this particular patch affecting SQL Server, since we're
patching the Indexing Service.
The Indexing Service is a base service for MicrosoftWindows 2000 or later
that extracts content from files and constructs an indexed catalog to
facilitate efficient and rapid searching. It is used for local searching
and can also be utilized on an IIS Web server to search remotely (with
custom web application code)
Please confirm that removing the patch allows your SQL Server to function
correctly. Open up a case with us if you're able to reproduce the problem.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||"Kevin McDonnell [MSFT]" wrote:[vbcol=seagreen]
> Please confirm that removing the patch allows your SQL Server to function
> correctly. Open up a case with us if you're able to reproduce the problem.[/vbcol
]
Kevin, Confirmed. As for "opening a case", I'd appreciate just a little
direction on exactly how to do that. I have looked with little success on th
e
web site and nothing just jumps out and shouts "log a case here". Clues are
sufficient (ususally).
d.|||Call Support Customer Care:
1-800-936-3500 (U.S. and Canada Only)
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
running MS SQLServer 2000 SP3. On doing this, certain data uploads began to
fail. Once this patch was removed, things began working again. Is there a
known issue with this patch? Has anyone else run across a similar issue? If
so, can someone suggest a work-around or other solution?
Thank you.
Daniel.Please confirm the patch you have installed/un-installed.
MS05-003 is not KB871259
http://www.microsoft.com/technet/se...n/MS05-003.mspx
is 871250.
This patch affect the Indexing Service and replaces the following file on
Win2k
Ciodm.dll
5.0.2195.6981
05-Nov-2004
04:41
68,880
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
My bad. I typoed. The patch applied is MS05-003 / 871250.
Suggestions or known issues?
Daniel.
"Kevin McDonnell [MSFT]" wrote:
> Please confirm the patch you have installed/un-installed.
> MS05-003 is not KB871259
> http://www.microsoft.com/technet/se...n/MS05-003.mspx
> is 871250.
> This patch affect the Indexing Service and replaces the following file on
> Win2k
> Ciodm.dll
> 5.0.2195.6981
> 05-Nov-2004
> 04:41
> 68,880
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||I'm not aware of this particular patch affecting SQL Server, since we're
patching the Indexing Service.
The Indexing Service is a base service for MicrosoftWindows 2000 or later
that extracts content from files and constructs an indexed catalog to
facilitate efficient and rapid searching. It is used for local searching
and can also be utilized on an IIS Web server to search remotely (with
custom web application code)
Please confirm that removing the patch allows your SQL Server to function
correctly. Open up a case with us if you're able to reproduce the problem.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||"Kevin McDonnell [MSFT]" wrote:[vbcol=seagreen]
> Please confirm that removing the patch allows your SQL Server to function
> correctly. Open up a case with us if you're able to reproduce the problem.[/vbcol
]
Kevin, Confirmed. As for "opening a case", I'd appreciate just a little
direction on exactly how to do that. I have looked with little success on th
e
web site and nothing just jumps out and shouts "log a case here". Clues are
sufficient (ususally).
d.|||Call Support Customer Care:
1-800-936-3500 (U.S. and Canada Only)
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Sunday, March 11, 2012
Apply sql2k post sp4 fix 2162 on cluster
I applied sql2k post sp4 fix 2040 and 2162 on active node of the cluster without error, the version number is 8.00.2162. When failover the cluster and double check version number again, it's 8.00.2040. That means fix 2162 didn't push to passive node. So I tried apply fix 2162 on current active node but stopped with KB904660(ENU) setup error: An error in updating your system has occurred. Can't find any log file, and OS is win2k3 enterprise edition with sp1. Anyone got similar issue?
You should get a higher build of Hotfix package. The issue you are reporting is a known bug and has been fixed in later builds.
thanks
Raja
Information on this page is posted as is and no warranty as to the accuracy of any of the presented information
Apply Service Pack Question
I have a couple of servers that are running SQL Server 2000 with no service
packs applied. I would like to apply SP3a to both of them. Are there any
possible/known problems that I should be aware of before attempting this.
This will be my first time doing this type of thing...
Thanks
EricMake sure you really read the documentation and readme etc that comes with the service pack! :-)
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Eric Stewart" <stewarte@.repsilverstate.com> wrote in message
news:uB95tpeZDHA.2236@.TK2MSFTNGP10.phx.gbl...
> I have a couple of servers that are running SQL Server 2000 with no service
> packs applied. I would like to apply SP3a to both of them. Are there any
> possible/known problems that I should be aware of before attempting this.
> This will be my first time doing this type of thing...
> Thanks
> Eric
>
packs applied. I would like to apply SP3a to both of them. Are there any
possible/known problems that I should be aware of before attempting this.
This will be my first time doing this type of thing...
Thanks
EricMake sure you really read the documentation and readme etc that comes with the service pack! :-)
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Eric Stewart" <stewarte@.repsilverstate.com> wrote in message
news:uB95tpeZDHA.2236@.TK2MSFTNGP10.phx.gbl...
> I have a couple of servers that are running SQL Server 2000 with no service
> packs applied. I would like to apply SP3a to both of them. Are there any
> possible/known problems that I should be aware of before attempting this.
> This will be my first time doing this type of thing...
> Thanks
> Eric
>
Thursday, March 8, 2012
applied dts files to sql server
I have a file named "posting.dts" in my c:\test\ directory,
how do I write a script to apply this dts package to SQL server "server1"?
thanksWhy do you need to write a script?
Can't you just right-click the Data Transformation Services folder in
EM and Select Open Package.
You could then browse to the .dts file and do a save as and save on the
Server?
Barry|||but i have many dts files, I want to apply them automatically with scripts.
I know how to apply dts script manually.
"Barry" wrote:
> Why do you need to write a script?
> Can't you just right-click the Data Transformation Services folder in
> EM and Select Open Package.
> You could then browse to the .dts file and do a save as and save on the
> Server?
> Barry
>
how do I write a script to apply this dts package to SQL server "server1"?
thanksWhy do you need to write a script?
Can't you just right-click the Data Transformation Services folder in
EM and Select Open Package.
You could then browse to the .dts file and do a save as and save on the
Server?
Barry|||but i have many dts files, I want to apply them automatically with scripts.
I know how to apply dts script manually.
"Barry" wrote:
> Why do you need to write a script?
> Can't you just right-click the Data Transformation Services folder in
> EM and Select Open Package.
> You could then browse to the .dts file and do a save as and save on the
> Server?
> Barry
>
Subscribe to:
Posts (Atom)