Two sql servers SERVER-1 and SERVER-2 each with database TESTDB and
identical table TESTTBL. I need to make sure that tables TESTTBL in
both servers are in sync by deleting records in SERVER-2.TESTDB.TESTTBL
which do not exist in SERVER-1.TESTDB.TESTTBL. The next requirement
would be to UPDATE and INSERT records in SERVER-2.TESTDB.TESTTBL to
make sure it to stay in sync with SERVER-2.TESTDB.TESTTBL . The
following C# code snippet fails. Is it possible to execute command
across two servers or am I wasting my time? Any help on this will be
appreciated.
string sSql= "delete SERVER-2.TESTDB.TESTTBL where
SERVER-2.TESTDB.TESTTBL.PRIMARY_FIELD1 not in (select PRIMARY_FIELD1
from SERVER-1.TESTDB.TESTTBL )";
SqlConnection thisConnection1 = null;
SqlConnection thisConnection2 = null;
SqlCommand thisCommand1 = null;
SqlCommand thisCommand2 = null;
thisConnection1 = new SqlConnection(connectionString1);
thisConnection1.Open();
thisConnection2 = new SqlConnection(connectionString2);
thisConnection2.Open();
thisCommand1 = new SqlCommand(sSql, thisConnection1);
try
{
thisCommand1.ExecuteNonQuery();
}
catch (SqlException oE)
{
MessageBox.Show(oE.Message.ToString());
}Have you consider using REPLICATION between tow servers?
<bkasmai@.gmail.com> wrote in message
news:1144070684.346122.72030@.v46g2000cwv.googlegroups.com...
> Two sql servers SERVER-1 and SERVER-2 each with database TESTDB and
> identical table TESTTBL. I need to make sure that tables TESTTBL in
> both servers are in sync by deleting records in SERVER-2.TESTDB.TESTTBL
> which do not exist in SERVER-1.TESTDB.TESTTBL. The next requirement
> would be to UPDATE and INSERT records in SERVER-2.TESTDB.TESTTBL to
> make sure it to stay in sync with SERVER-2.TESTDB.TESTTBL . The
> following C# code snippet fails. Is it possible to execute command
> across two servers or am I wasting my time? Any help on this will be
> appreciated.
> string sSql= "delete SERVER-2.TESTDB.TESTTBL where
> SERVER-2.TESTDB.TESTTBL.PRIMARY_FIELD1 not in (select PRIMARY_FIELD1
> from SERVER-1.TESTDB.TESTTBL )";
> SqlConnection thisConnection1 = null;
> SqlConnection thisConnection2 = null;
> SqlCommand thisCommand1 = null;
> SqlCommand thisCommand2 = null;
> thisConnection1 = new SqlConnection(connectionString1);
> thisConnection1.Open();
> thisConnection2 = new SqlConnection(connectionString2);
> thisConnection2.Open();
> thisCommand1 = new SqlCommand(sSql, thisConnection1);
> try
> {
> thisCommand1.ExecuteNonQuery();
> }
> catch (SqlException oE)
> {
> MessageBox.Show(oE.Message.ToString());
> }
>|||Yes. Past experience prevent me from using replication.
SERVER-1.TESTDB1 and SERVER-2.TESTDB are not identical but
SERVER-1.TESTDB1.TESTTBL and SERVER-1.TESTDB1.TESTTBL must be in sync.|||Well, another option is to BACKUP LOG file on the source SERVER and
RESTORE it on destination. But I see the problem here because if I remember
well the destination SERVER must be read only....
<bkasmai@.gmail.com> wrote in message
news:1144073079.759225.46870@.e56g2000cwe.googlegroups.com...
> Yes. Past experience prevent me from using replication.
> SERVER-1.TESTDB1 and SERVER-2.TESTDB are not identical but
> SERVER-1.TESTDB1.TESTTBL and SERVER-1.TESTDB1.TESTTBL must be in sync.
>|||The sync needs to be done every hour through a application written in
c# !
Showing posts with label servers. Show all posts
Showing posts with label servers. Show all posts
Friday, March 30, 2012
MS SQL2000 - synchronizing tables across two sql servers - wasting my time?
Two sql servers SERVER-1 and SERVER-2 each with database TESTDB and
identical table TESTTBL. I need to make sure that tables TESTTBL in
both servers are in sync by deleting records in SERVER-2.TESTDB.TESTTBL
which do not exist in SERVER-1.TESTDB.TESTTBL. The next requirement
would be to UPDATE and INSERT records in SERVER-2.TESTDB.TESTTBL to
make sure it to stay in sync with SERVER-2.TESTDB.TESTTBL . The
following C# code snippet fails. Is it possible to execute command
across two servers or am I wasting my time? Any help on this will be
appreciated.
string sSql= "delete SERVER-2.TESTDB.TESTTBL where
SERVER-2.TESTDB.TESTTBL.PRIMARY_FIELD1 not in (select PRIMARY_FIELD1
from SERVER-1.TESTDB.TESTTBL )";
SqlConnection thisConnection1 = null;
SqlConnection thisConnection2 = null;
SqlCommand thisCommand1 = null;
SqlCommand thisCommand2 = null;
thisConnection1 = new SqlConnection(connectionString1);
thisConnection1.Open();
thisConnection2 = new SqlConnection(connectionString2);
thisConnection2.Open();
thisCommand1 = new SqlCommand(sSql, thisConnection1);
try
{
thisCommand1.ExecuteNonQuery();
}
catch (SqlException oE)
{
MessageBox.Show(oE.Message.ToString());
}Have you consider using REPLICATION between tow servers?
<bkasmai@.gmail.com> wrote in message
news:1144070684.346122.72030@.v46g2000cwv.googlegroups.com...
> Two sql servers SERVER-1 and SERVER-2 each with database TESTDB and
> identical table TESTTBL. I need to make sure that tables TESTTBL in
> both servers are in sync by deleting records in SERVER-2.TESTDB.TESTTBL
> which do not exist in SERVER-1.TESTDB.TESTTBL. The next requirement
> would be to UPDATE and INSERT records in SERVER-2.TESTDB.TESTTBL to
> make sure it to stay in sync with SERVER-2.TESTDB.TESTTBL . The
> following C# code snippet fails. Is it possible to execute command
> across two servers or am I wasting my time? Any help on this will be
> appreciated.
> string sSql= "delete SERVER-2.TESTDB.TESTTBL where
> SERVER-2.TESTDB.TESTTBL.PRIMARY_FIELD1 not in (select PRIMARY_FIELD1
> from SERVER-1.TESTDB.TESTTBL )";
> SqlConnection thisConnection1 = null;
> SqlConnection thisConnection2 = null;
> SqlCommand thisCommand1 = null;
> SqlCommand thisCommand2 = null;
> thisConnection1 = new SqlConnection(connectionString1);
> thisConnection1.Open();
> thisConnection2 = new SqlConnection(connectionString2);
> thisConnection2.Open();
> thisCommand1 = new SqlCommand(sSql, thisConnection1);
> try
> {
> thisCommand1.ExecuteNonQuery();
> }
> catch (SqlException oE)
> {
> MessageBox.Show(oE.Message.ToString());
> }
>|||Yes. Past experience prevent me from using replication.
SERVER-1.TESTDB1 and SERVER-2.TESTDB are not identical but
SERVER-1.TESTDB1.TESTTBL and SERVER-1.TESTDB1.TESTTBL must be in sync.|||Well, another option is to BACKUP LOG file on the source SERVER and
RESTORE it on destination. But I see the problem here because if I remember
well the destination SERVER must be read only....
<bkasmai@.gmail.com> wrote in message
news:1144073079.759225.46870@.e56g2000cwe.googlegroups.com...
> Yes. Past experience prevent me from using replication.
> SERVER-1.TESTDB1 and SERVER-2.TESTDB are not identical but
> SERVER-1.TESTDB1.TESTTBL and SERVER-1.TESTDB1.TESTTBL must be in sync.
>|||The sync needs to be done every hour through a application written in
c# !sql
identical table TESTTBL. I need to make sure that tables TESTTBL in
both servers are in sync by deleting records in SERVER-2.TESTDB.TESTTBL
which do not exist in SERVER-1.TESTDB.TESTTBL. The next requirement
would be to UPDATE and INSERT records in SERVER-2.TESTDB.TESTTBL to
make sure it to stay in sync with SERVER-2.TESTDB.TESTTBL . The
following C# code snippet fails. Is it possible to execute command
across two servers or am I wasting my time? Any help on this will be
appreciated.
string sSql= "delete SERVER-2.TESTDB.TESTTBL where
SERVER-2.TESTDB.TESTTBL.PRIMARY_FIELD1 not in (select PRIMARY_FIELD1
from SERVER-1.TESTDB.TESTTBL )";
SqlConnection thisConnection1 = null;
SqlConnection thisConnection2 = null;
SqlCommand thisCommand1 = null;
SqlCommand thisCommand2 = null;
thisConnection1 = new SqlConnection(connectionString1);
thisConnection1.Open();
thisConnection2 = new SqlConnection(connectionString2);
thisConnection2.Open();
thisCommand1 = new SqlCommand(sSql, thisConnection1);
try
{
thisCommand1.ExecuteNonQuery();
}
catch (SqlException oE)
{
MessageBox.Show(oE.Message.ToString());
}Have you consider using REPLICATION between tow servers?
<bkasmai@.gmail.com> wrote in message
news:1144070684.346122.72030@.v46g2000cwv.googlegroups.com...
> Two sql servers SERVER-1 and SERVER-2 each with database TESTDB and
> identical table TESTTBL. I need to make sure that tables TESTTBL in
> both servers are in sync by deleting records in SERVER-2.TESTDB.TESTTBL
> which do not exist in SERVER-1.TESTDB.TESTTBL. The next requirement
> would be to UPDATE and INSERT records in SERVER-2.TESTDB.TESTTBL to
> make sure it to stay in sync with SERVER-2.TESTDB.TESTTBL . The
> following C# code snippet fails. Is it possible to execute command
> across two servers or am I wasting my time? Any help on this will be
> appreciated.
> string sSql= "delete SERVER-2.TESTDB.TESTTBL where
> SERVER-2.TESTDB.TESTTBL.PRIMARY_FIELD1 not in (select PRIMARY_FIELD1
> from SERVER-1.TESTDB.TESTTBL )";
> SqlConnection thisConnection1 = null;
> SqlConnection thisConnection2 = null;
> SqlCommand thisCommand1 = null;
> SqlCommand thisCommand2 = null;
> thisConnection1 = new SqlConnection(connectionString1);
> thisConnection1.Open();
> thisConnection2 = new SqlConnection(connectionString2);
> thisConnection2.Open();
> thisCommand1 = new SqlCommand(sSql, thisConnection1);
> try
> {
> thisCommand1.ExecuteNonQuery();
> }
> catch (SqlException oE)
> {
> MessageBox.Show(oE.Message.ToString());
> }
>|||Yes. Past experience prevent me from using replication.
SERVER-1.TESTDB1 and SERVER-2.TESTDB are not identical but
SERVER-1.TESTDB1.TESTTBL and SERVER-1.TESTDB1.TESTTBL must be in sync.|||Well, another option is to BACKUP LOG file on the source SERVER and
RESTORE it on destination. But I see the problem here because if I remember
well the destination SERVER must be read only....
<bkasmai@.gmail.com> wrote in message
news:1144073079.759225.46870@.e56g2000cwe.googlegroups.com...
> Yes. Past experience prevent me from using replication.
> SERVER-1.TESTDB1 and SERVER-2.TESTDB are not identical but
> SERVER-1.TESTDB1.TESTTBL and SERVER-1.TESTDB1.TESTTBL must be in sync.
>|||The sync needs to be done every hour through a application written in
c# !sql
MS SQL2000 - synchronizing tables across two sql servers - wasting my time?
Two sql servers SERVER-1 and SERVER-2 each with database TESTDB and
identical table TESTTBL. I need to make sure that tables TESTTBL in
both servers are in sync by deleting records in SERVER-2.TESTDB.TESTTBL
which do not exist in SERVER-1.TESTDB.TESTTBL. The next requirement
would be to UPDATE and INSERT records in SERVER-2.TESTDB.TESTTBL to
make sure it to stay in sync with SERVER-2.TESTDB.TESTTBL . The
following C# code snippet fails. Is it possible to execute command
across two servers or am I wasting my time? Any help on this will be
appreciated.
string sSql= "delete SERVER-2.TESTDB.TESTTBL where
SERVER-2.TESTDB.TESTTBL.PRIMARY_FIELD1 not in (select PRIMARY_FIELD1
from SERVER-1.TESTDB.TESTTBL )";
SqlConnection thisConnection1 = null;
SqlConnection thisConnection2 = null;
SqlCommand thisCommand1 = null;
SqlCommand thisCommand2 = null;
thisConnection1 = new SqlConnection(connectionString1);
thisConnection1.Open();
thisConnection2 = new SqlConnection(connectionString2);
thisConnection2.Open();
thisCommand1 = new SqlCommand(sSql, thisConnection1);
try
{
thisCommand1.ExecuteNonQuery();
}
catch (SqlException oE)
{
MessageBox.Show(oE.Message.ToString());
}
Have you consider using REPLICATION between tow servers?
<bkasmai@.gmail.com> wrote in message
news:1144070684.346122.72030@.v46g2000cwv.googlegro ups.com...
> Two sql servers SERVER-1 and SERVER-2 each with database TESTDB and
> identical table TESTTBL. I need to make sure that tables TESTTBL in
> both servers are in sync by deleting records in SERVER-2.TESTDB.TESTTBL
> which do not exist in SERVER-1.TESTDB.TESTTBL. The next requirement
> would be to UPDATE and INSERT records in SERVER-2.TESTDB.TESTTBL to
> make sure it to stay in sync with SERVER-2.TESTDB.TESTTBL . The
> following C# code snippet fails. Is it possible to execute command
> across two servers or am I wasting my time? Any help on this will be
> appreciated.
> string sSql= "delete SERVER-2.TESTDB.TESTTBL where
> SERVER-2.TESTDB.TESTTBL.PRIMARY_FIELD1 not in (select PRIMARY_FIELD1
> from SERVER-1.TESTDB.TESTTBL )";
> SqlConnection thisConnection1 = null;
> SqlConnection thisConnection2 = null;
> SqlCommand thisCommand1 = null;
> SqlCommand thisCommand2 = null;
> thisConnection1 = new SqlConnection(connectionString1);
> thisConnection1.Open();
> thisConnection2 = new SqlConnection(connectionString2);
> thisConnection2.Open();
> thisCommand1 = new SqlCommand(sSql, thisConnection1);
> try
> {
> thisCommand1.ExecuteNonQuery();
> }
> catch (SqlException oE)
> {
> MessageBox.Show(oE.Message.ToString());
> }
>
|||Yes. Past experience prevent me from using replication.
SERVER-1.TESTDB1 and SERVER-2.TESTDB are not identical but
SERVER-1.TESTDB1.TESTTBL and SERVER-1.TESTDB1.TESTTBL must be in sync.
|||Well, another option is to BACKUP LOG file on the source SERVER and
RESTORE it on destination. But I see the problem here because if I remember
well the destination SERVER must be read only....
<bkasmai@.gmail.com> wrote in message
news:1144073079.759225.46870@.e56g2000cwe.googlegro ups.com...
> Yes. Past experience prevent me from using replication.
> SERVER-1.TESTDB1 and SERVER-2.TESTDB are not identical but
> SERVER-1.TESTDB1.TESTTBL and SERVER-1.TESTDB1.TESTTBL must be in sync.
>
|||The sync needs to be done every hour through a application written in
c# !
identical table TESTTBL. I need to make sure that tables TESTTBL in
both servers are in sync by deleting records in SERVER-2.TESTDB.TESTTBL
which do not exist in SERVER-1.TESTDB.TESTTBL. The next requirement
would be to UPDATE and INSERT records in SERVER-2.TESTDB.TESTTBL to
make sure it to stay in sync with SERVER-2.TESTDB.TESTTBL . The
following C# code snippet fails. Is it possible to execute command
across two servers or am I wasting my time? Any help on this will be
appreciated.
string sSql= "delete SERVER-2.TESTDB.TESTTBL where
SERVER-2.TESTDB.TESTTBL.PRIMARY_FIELD1 not in (select PRIMARY_FIELD1
from SERVER-1.TESTDB.TESTTBL )";
SqlConnection thisConnection1 = null;
SqlConnection thisConnection2 = null;
SqlCommand thisCommand1 = null;
SqlCommand thisCommand2 = null;
thisConnection1 = new SqlConnection(connectionString1);
thisConnection1.Open();
thisConnection2 = new SqlConnection(connectionString2);
thisConnection2.Open();
thisCommand1 = new SqlCommand(sSql, thisConnection1);
try
{
thisCommand1.ExecuteNonQuery();
}
catch (SqlException oE)
{
MessageBox.Show(oE.Message.ToString());
}
Have you consider using REPLICATION between tow servers?
<bkasmai@.gmail.com> wrote in message
news:1144070684.346122.72030@.v46g2000cwv.googlegro ups.com...
> Two sql servers SERVER-1 and SERVER-2 each with database TESTDB and
> identical table TESTTBL. I need to make sure that tables TESTTBL in
> both servers are in sync by deleting records in SERVER-2.TESTDB.TESTTBL
> which do not exist in SERVER-1.TESTDB.TESTTBL. The next requirement
> would be to UPDATE and INSERT records in SERVER-2.TESTDB.TESTTBL to
> make sure it to stay in sync with SERVER-2.TESTDB.TESTTBL . The
> following C# code snippet fails. Is it possible to execute command
> across two servers or am I wasting my time? Any help on this will be
> appreciated.
> string sSql= "delete SERVER-2.TESTDB.TESTTBL where
> SERVER-2.TESTDB.TESTTBL.PRIMARY_FIELD1 not in (select PRIMARY_FIELD1
> from SERVER-1.TESTDB.TESTTBL )";
> SqlConnection thisConnection1 = null;
> SqlConnection thisConnection2 = null;
> SqlCommand thisCommand1 = null;
> SqlCommand thisCommand2 = null;
> thisConnection1 = new SqlConnection(connectionString1);
> thisConnection1.Open();
> thisConnection2 = new SqlConnection(connectionString2);
> thisConnection2.Open();
> thisCommand1 = new SqlCommand(sSql, thisConnection1);
> try
> {
> thisCommand1.ExecuteNonQuery();
> }
> catch (SqlException oE)
> {
> MessageBox.Show(oE.Message.ToString());
> }
>
|||Yes. Past experience prevent me from using replication.
SERVER-1.TESTDB1 and SERVER-2.TESTDB are not identical but
SERVER-1.TESTDB1.TESTTBL and SERVER-1.TESTDB1.TESTTBL must be in sync.
|||Well, another option is to BACKUP LOG file on the source SERVER and
RESTORE it on destination. But I see the problem here because if I remember
well the destination SERVER must be read only....
<bkasmai@.gmail.com> wrote in message
news:1144073079.759225.46870@.e56g2000cwe.googlegro ups.com...
> Yes. Past experience prevent me from using replication.
> SERVER-1.TESTDB1 and SERVER-2.TESTDB are not identical but
> SERVER-1.TESTDB1.TESTTBL and SERVER-1.TESTDB1.TESTTBL must be in sync.
>
|||The sync needs to be done every hour through a application written in
c# !
Wednesday, March 28, 2012
MS SQL Server, Linked Server to Pervasive
Hello all,
I am new to the forums and I have a question regarding linked servers. I am searching for the method of adding a Linked Server from MS SQL Server to a Pervasive database (specifically, the DEMODATA database that one gets after installing the Pervasive trial).
Specifically, I am looking for
1. What (if any) special drivers do I need?
2. What DSNs (if any) are necessary, besides DEMODATA with the Pervasive ODBC Engine Interface driver?
3. What parameters need I provide to sp_addlinkedserver?
Any input would be very much appreciated. Thanks.
RobRefer to books online for linked server and heterogeneous data sources topics.
I am new to the forums and I have a question regarding linked servers. I am searching for the method of adding a Linked Server from MS SQL Server to a Pervasive database (specifically, the DEMODATA database that one gets after installing the Pervasive trial).
Specifically, I am looking for
1. What (if any) special drivers do I need?
2. What DSNs (if any) are necessary, besides DEMODATA with the Pervasive ODBC Engine Interface driver?
3. What parameters need I provide to sp_addlinkedserver?
Any input would be very much appreciated. Thanks.
RobRefer to books online for linked server and heterogeneous data sources topics.
MS SQL Server Memory Supported
We are using SQL 2000 and being moved from old NT Servers having 2 G of RAM to new hardware with Win 2003 installed and 8GB of RAM.
Now can SQL 2000 use more than 2G of RAM on Win2003, if yes do we need to do any settings
Pls advise
Thanks
sanjay
Hello,
Only SQL server 2000 Enterprise Edition support more than 2 GB RAM. Other
editions will support only a
maximum of 2 GB.
If it is Enterprise edition then have a look into the below site to enable
more than 2 GB RAM to SQL server using AWE:-
http://www.sql-server-performance.com/awe_memory.asp
Thanks
Hari
MCDBA
"Sanjay" <Sanjay@.discussions.microsoft.com> wrote in message
news:DFD9B463-7A8F-48BA-BB9B-AB52BB35310F@.microsoft.com...
> We are using SQL 2000 and being moved from old NT Servers having 2 G of
RAM to new hardware with Win 2003 installed and 8GB of RAM.
> Now can SQL 2000 use more than 2G of RAM on Win2003, if yes do we need to
do any settings
> Pls advise
> Thanks
> sanjay
Now can SQL 2000 use more than 2G of RAM on Win2003, if yes do we need to do any settings
Pls advise
Thanks
sanjay
Hello,
Only SQL server 2000 Enterprise Edition support more than 2 GB RAM. Other
editions will support only a
maximum of 2 GB.
If it is Enterprise edition then have a look into the below site to enable
more than 2 GB RAM to SQL server using AWE:-
http://www.sql-server-performance.com/awe_memory.asp
Thanks
Hari
MCDBA
"Sanjay" <Sanjay@.discussions.microsoft.com> wrote in message
news:DFD9B463-7A8F-48BA-BB9B-AB52BB35310F@.microsoft.com...
> We are using SQL 2000 and being moved from old NT Servers having 2 G of
RAM to new hardware with Win 2003 installed and 8GB of RAM.
> Now can SQL 2000 use more than 2G of RAM on Win2003, if yes do we need to
do any settings
> Pls advise
> Thanks
> sanjay
MS SQL Server Memory Supported
We are using SQL 2000 and being moved from old NT Servers having 2 G of RAM to new hardware with Win 2003 installed and 8GB of RAM.
Now can SQL 2000 use more than 2G of RAM on Win2003, if yes do we need to do any settings
Pls advise
Thanks
sanjayHello,
Only SQL server 2000 Enterprise Edition support more than 2 GB RAM. Other
editions will support only a
maximum of 2 GB.
If it is Enterprise edition then have a look into the below site to enable
more than 2 GB RAM to SQL server using AWE:-
http://www.sql-server-performance.com/awe_memory.asp
Thanks
Hari
MCDBA
"Sanjay" <Sanjay@.discussions.microsoft.com> wrote in message
news:DFD9B463-7A8F-48BA-BB9B-AB52BB35310F@.microsoft.com...
> We are using SQL 2000 and being moved from old NT Servers having 2 G of
RAM to new hardware with Win 2003 installed and 8GB of RAM.
> Now can SQL 2000 use more than 2G of RAM on Win2003, if yes do we need to
do any settings
> Pls advise
> Thanks
> sanjaysql
Now can SQL 2000 use more than 2G of RAM on Win2003, if yes do we need to do any settings
Pls advise
Thanks
sanjayHello,
Only SQL server 2000 Enterprise Edition support more than 2 GB RAM. Other
editions will support only a
maximum of 2 GB.
If it is Enterprise edition then have a look into the below site to enable
more than 2 GB RAM to SQL server using AWE:-
http://www.sql-server-performance.com/awe_memory.asp
Thanks
Hari
MCDBA
"Sanjay" <Sanjay@.discussions.microsoft.com> wrote in message
news:DFD9B463-7A8F-48BA-BB9B-AB52BB35310F@.microsoft.com...
> We are using SQL 2000 and being moved from old NT Servers having 2 G of
RAM to new hardware with Win 2003 installed and 8GB of RAM.
> Now can SQL 2000 use more than 2G of RAM on Win2003, if yes do we need to
do any settings
> Pls advise
> Thanks
> sanjaysql
MS SQL Server Memory Supported
We are using SQL 2000 and being moved from old NT Servers having 2 G of RAM
to new hardware with Win 2003 installed and 8GB of RAM.
Now can SQL 2000 use more than 2G of RAM on Win2003, if yes do we need to do
any settings
Pls advise
Thanks
sanjayHello,
Only SQL server 2000 Enterprise Edition support more than 2 GB RAM. Other
editions will support only a
maximum of 2 GB.
If it is Enterprise edition then have a look into the below site to enable
more than 2 GB RAM to SQL server using AWE:-
http://www.sql-server-performance.com/awe_memory.asp
Thanks
Hari
MCDBA
"Sanjay" <Sanjay@.discussions.microsoft.com> wrote in message
news:DFD9B463-7A8F-48BA-BB9B-AB52BB35310F@.microsoft.com...
> We are using SQL 2000 and being moved from old NT Servers having 2 G of
RAM to new hardware with Win 2003 installed and 8GB of RAM.
> Now can SQL 2000 use more than 2G of RAM on Win2003, if yes do we need to
do any settings
> Pls advise
> Thanks
> sanjay
to new hardware with Win 2003 installed and 8GB of RAM.
Now can SQL 2000 use more than 2G of RAM on Win2003, if yes do we need to do
any settings
Pls advise
Thanks
sanjayHello,
Only SQL server 2000 Enterprise Edition support more than 2 GB RAM. Other
editions will support only a
maximum of 2 GB.
If it is Enterprise edition then have a look into the below site to enable
more than 2 GB RAM to SQL server using AWE:-
http://www.sql-server-performance.com/awe_memory.asp
Thanks
Hari
MCDBA
"Sanjay" <Sanjay@.discussions.microsoft.com> wrote in message
news:DFD9B463-7A8F-48BA-BB9B-AB52BB35310F@.microsoft.com...
> We are using SQL 2000 and being moved from old NT Servers having 2 G of
RAM to new hardware with Win 2003 installed and 8GB of RAM.
> Now can SQL 2000 use more than 2G of RAM on Win2003, if yes do we need to
do any settings
> Pls advise
> Thanks
> sanjay
Monday, March 26, 2012
MS SQL Server Build
Hi,
I have some servers with MS SQL. I don't know their history. So, some of them have build no. 760 and the others have build no.818 . Can anybody explain me differences? A can't find any information.
Thanks a lot
Jan
http://www.aspfaq.com/show.asp?id=2160
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"systemspecialist" <systemspecialist@.centrum.cz> wrote in message
news:DA48B9D1-D659-44C7-AA11-990479F2C5E0@.microsoft.com...
> Hi,
> I have some servers with MS SQL. I don't know their history. So, some of them have build no. 760 and the
others have build no.818 . Can anybody explain me differences? A can't find any information.
> Thanks a lot
> Jan
I have some servers with MS SQL. I don't know their history. So, some of them have build no. 760 and the others have build no.818 . Can anybody explain me differences? A can't find any information.
Thanks a lot
Jan
http://www.aspfaq.com/show.asp?id=2160
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"systemspecialist" <systemspecialist@.centrum.cz> wrote in message
news:DA48B9D1-D659-44C7-AA11-990479F2C5E0@.microsoft.com...
> Hi,
> I have some servers with MS SQL. I don't know their history. So, some of them have build no. 760 and the
others have build no.818 . Can anybody explain me differences? A can't find any information.
> Thanks a lot
> Jan
MS SQL Server Build
Hi
I have some servers with MS SQL. I don't know their history. So, some of them have build no. 760 and the others have build no.818 . Can anybody explain me differences? A can't find any information.
Thanks a lo
Janhttp://www.aspfaq.com/show.asp?id=2160
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"systemspecialist" <systemspecialist@.centrum.cz> wrote in message
news:DA48B9D1-D659-44C7-AA11-990479F2C5E0@.microsoft.com...
> Hi,
> I have some servers with MS SQL. I don't know their history. So, some of them have build no. 760 and the
others have build no.818 . Can anybody explain me differences? A can't find any information.
> Thanks a lot
> Jan
I have some servers with MS SQL. I don't know their history. So, some of them have build no. 760 and the others have build no.818 . Can anybody explain me differences? A can't find any information.
Thanks a lo
Janhttp://www.aspfaq.com/show.asp?id=2160
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"systemspecialist" <systemspecialist@.centrum.cz> wrote in message
news:DA48B9D1-D659-44C7-AA11-990479F2C5E0@.microsoft.com...
> Hi,
> I have some servers with MS SQL. I don't know their history. So, some of them have build no. 760 and the
others have build no.818 . Can anybody explain me differences? A can't find any information.
> Thanks a lot
> Jan
MS SQL Server Build
Hi,
I have some servers with MS SQL. I don't know their history. So, some of the
m have build no. 760 and the others have build no.818 . Can anybody explain
me differences? A can't find any information.
Thanks a lot
Janhttp://www.aspfaq.com/show.asp?id=2160
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"systemspecialist" <systemspecialist@.centrum.cz> wrote in message
news:DA48B9D1-D659-44C7-AA11-990479F2C5E0@.microsoft.com...
> Hi,
> I have some servers with MS SQL. I don't know their history. So, some of them have
build no. 760 and the
others have build no.818 . Can anybody explain me differences? A can't find any information.
> Thanks a lot
> Jan
I have some servers with MS SQL. I don't know their history. So, some of the
m have build no. 760 and the others have build no.818 . Can anybody explain
me differences? A can't find any information.
Thanks a lot
Janhttp://www.aspfaq.com/show.asp?id=2160
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"systemspecialist" <systemspecialist@.centrum.cz> wrote in message
news:DA48B9D1-D659-44C7-AA11-990479F2C5E0@.microsoft.com...
> Hi,
> I have some servers with MS SQL. I don't know their history. So, some of them have
build no. 760 and the
others have build no.818 . Can anybody explain me differences? A can't find any information.
> Thanks a lot
> Jan
Friday, March 23, 2012
MS SQL Server 2005 SP2 Problems with SSIS packages
I installed SP2 to one of our servers to see what we'd need to do for our Production systems. The server in question is used for a log shipped copy of production, SSRS, SSIS and general duty stuff. I got errors in two areas during the installation -- 1 dealing with SSNS (don't use it yet on that server) and the second being the Client product.
After a reboot I went into a Business Studio solution I've been working on (and using) for several months. None of my packages are working--each having the following problem:
Unable to cast COM object of type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.PackageNeutralClass' to interface type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSContainer90'.
This operation failed because the QueryInterface call on the COM component for the interface with IID '{8BDFE892-E9D8-4D23-9739-DA807BCDC2AC}'
failed due to the following error: Library not registered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED))..
It seems to be in the designer as it is unable to display the the graphical version but it does let me switch to the code view.
What is the easiest way to troubleshoot and/or fix this?
For some reason it didn't register the new DTS.DLL correctly. Running
regsvr32 “C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll"
made the problem go away. Things that make you go 'hmmmmmmmmm'.
I wonder what else is busted...
Wednesday, March 21, 2012
MS SQL Server 2000 replication deployment
Hi
I want to implement transactional replication on 2 MS SQL Servers 2000
(SP3). Is there any good guide available that discusses crucial points in
this endeavour (e.g. possible topologies, what and how needs to be monitored,
potential issues to avoid, what to do in case of failures etc.)? I need a
document that focuses on moving the replication into production environment.
I'm especially interested in alternative means of monitoring the replication
rather than the built-in one.
Many thanks,
Oskar
You can check BOL, do a search on MSDN for transactional replication. You
might want to consider my book
Hilary Cotter
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
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:3F9E5C48-79C8-4D76-87C8-B9C2ABC6C840@.microsoft.com...
> Hi
> I want to implement transactional replication on 2 MS SQL Servers 2000
> (SP3). Is there any good guide available that discusses crucial points in
> this endeavour (e.g. possible topologies, what and how needs to be
monitored,
> potential issues to avoid, what to do in case of failures etc.)? I need a
> document that focuses on moving the replication into production
environment.
> I'm especially interested in alternative means of monitoring the
replication
> rather than the built-in one.
> --
> Many thanks,
> Oskar
>
|||Yeah, but are you completely sure that these sources give answers to the
specific questions I have? So far I was unable to find answers to my
questions in BOL.
"Hilary Cotter" wrote:
> You can check BOL, do a search on MSDN for transactional replication. You
> might want to consider my book
> --
> Hilary Cotter
> 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
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:3F9E5C48-79C8-4D76-87C8-B9C2ABC6C840@.microsoft.com...
> monitored,
> environment.
> replication
>
>
I want to implement transactional replication on 2 MS SQL Servers 2000
(SP3). Is there any good guide available that discusses crucial points in
this endeavour (e.g. possible topologies, what and how needs to be monitored,
potential issues to avoid, what to do in case of failures etc.)? I need a
document that focuses on moving the replication into production environment.
I'm especially interested in alternative means of monitoring the replication
rather than the built-in one.
Many thanks,
Oskar
You can check BOL, do a search on MSDN for transactional replication. You
might want to consider my book
Hilary Cotter
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
"Oskar" <Oskar@.discussions.microsoft.com> wrote in message
news:3F9E5C48-79C8-4D76-87C8-B9C2ABC6C840@.microsoft.com...
> Hi
> I want to implement transactional replication on 2 MS SQL Servers 2000
> (SP3). Is there any good guide available that discusses crucial points in
> this endeavour (e.g. possible topologies, what and how needs to be
monitored,
> potential issues to avoid, what to do in case of failures etc.)? I need a
> document that focuses on moving the replication into production
environment.
> I'm especially interested in alternative means of monitoring the
replication
> rather than the built-in one.
> --
> Many thanks,
> Oskar
>
|||Yeah, but are you completely sure that these sources give answers to the
specific questions I have? So far I was unable to find answers to my
questions in BOL.
"Hilary Cotter" wrote:
> You can check BOL, do a search on MSDN for transactional replication. You
> might want to consider my book
> --
> Hilary Cotter
> 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
> "Oskar" <Oskar@.discussions.microsoft.com> wrote in message
> news:3F9E5C48-79C8-4D76-87C8-B9C2ABC6C840@.microsoft.com...
> monitored,
> environment.
> replication
>
>
Monday, March 12, 2012
MS SQL Linked Servers(Linking MySQL to MS SQL) Collation problem.
Hello,
I have a problem. I've linked MySql server to MsSql, in MySql I have a
table with Latvian data(character set is ucs2, ucs2_general_ci) and
the problem is that when I use openquery to read data from MySQL
server, some characters are not translated correctly! I receive
question symbols instead of Latvian special characters.
Maybe someone had this kind of problem with collation?P?vels Mihailovs (iceravenlv@.gmail.com) writes:
Since I don't work with MySQL myself, it's difficult to say what is
going on. But if MySQL has a notion of collation, and the collation is
ucs2_general_ci, it sounds like MySQL returns Unicode data. One would
expect that to arrive unscathed. What is you collation on the SQL
Server side?
>
Since I don't work with MySQL myself, it's difficult to say what is
going on. But if MySQL has a notion of collation, and the collation is
ucs2_general_ci, it sounds like MySQL returns Unicode data. One would
expect that to arrive unscathed. What is you collation on the SQL
Server side?
>
The stored procedure sp_serveroption permits you to set options for
linked servers, and two of them relates to collations. You could play
around with these and see what happens. Please look in Books Online
for details.
>
--
Erland Sommarskog, SQL Server MVP, esq...@.sommarskog.se
>
Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
on the MS SQL server i'm using Latvian_CI_AI, but some databases are
set to Latvian_CI_AS collation (sorry db admin can't explain why they
are using it).
I've tried using different collation option, I've checked all 1257 and
other collation, but result was almost the same. :/
I have a problem. I've linked MySql server to MsSql, in MySql I have a
table with Latvian data(character set is ucs2, ucs2_general_ci) and
the problem is that when I use openquery to read data from MySQL
server, some characters are not translated correctly! I receive
question symbols instead of Latvian special characters.
Maybe someone had this kind of problem with collation?P?vels Mihailovs (iceravenlv@.gmail.com) writes:
Quote:
Originally Posted by
I have a problem. I've linked MySql server to MsSql, in MySql I have a
table with Latvian data(character set is ucs2, ucs2_general_ci) and
the problem is that when I use openquery to read data from MySQL
server, some characters are not translated correctly! I receive
question symbols instead of Latvian special characters.
Maybe someone had this kind of problem with collation?
Since I don't work with MySQL myself, it's difficult to say what is
going on. But if MySQL has a notion of collation, and the collation is
ucs2_general_ci, it sounds like MySQL returns Unicode data. One would
expect that to arrive unscathed. What is you collation on the SQL
Server side?
The stored procedure sp_serveroption permits you to set options for
linked servers, and two of them relates to collations. You could play
around with these and see what happens. Please look in Books Online
for details.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||On Jun 22, 1:16 am, Erland Sommarskog <esq...@.sommarskog.sewrote:
Quote:
Originally Posted by
P?vels Mihailovs (icerave...@.gmail.com) writes:
Quote:
Originally Posted by
I have a problem. I've linked MySql server to MsSql, in MySql I have a
table with Latvian data(character set is ucs2, ucs2_general_ci) and
the problem is that when I use openquery to read data from MySQL
server, some characters are not translated correctly! I receive
question symbols instead of Latvian special characters.
Maybe someone had this kind of problem with collation?
>
Since I don't work with MySQL myself, it's difficult to say what is
going on. But if MySQL has a notion of collation, and the collation is
ucs2_general_ci, it sounds like MySQL returns Unicode data. One would
expect that to arrive unscathed. What is you collation on the SQL
Server side?
>
The stored procedure sp_serveroption permits you to set options for
linked servers, and two of them relates to collations. You could play
around with these and see what happens. Please look in Books Online
for details.
>
--
Erland Sommarskog, SQL Server MVP, esq...@.sommarskog.se
>
Books Online for SQL Server 2005 athttp://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books...
Books Online for SQL Server 2000 athttp://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
on the MS SQL server i'm using Latvian_CI_AI, but some databases are
set to Latvian_CI_AS collation (sorry db admin can't explain why they
are using it).
I've tried using different collation option, I've checked all 1257 and
other collation, but result was almost the same. :/
MS SQL Jobs
Hi SQL Guru's
I am trying to run a job on Multiple SQL Servers in a domain.I am setting the job on my system,but the Radio button "Target Multiple Servers" is disabled.How do I enable the radio button "Target Multiple Servers".
Please let me know if this is possible.
Best Regards
SK.you have to ensure that your machine is a master and that you have
registered servers to be targets.
Right click sql server agent -- Multi Server Administration -- Make this a master.
During this process you will be asked to create a MSX operator. and to enlist targets. the targets will need to be pre-registered with your master's instance and then define the jobs on the master and then you will be able to target multiple servers.
understand that this process is designed to return all job history to the master so you can check the progress of job operations from one place. however, just as with the highlander, there can be only one.... meaning that a target cannot be a master for other servers.
:confused: and dont forget to check books online,
BOOKS ONLINE {Multiserver Administration}
I am trying to run a job on Multiple SQL Servers in a domain.I am setting the job on my system,but the Radio button "Target Multiple Servers" is disabled.How do I enable the radio button "Target Multiple Servers".
Please let me know if this is possible.
Best Regards
SK.you have to ensure that your machine is a master and that you have
registered servers to be targets.
Right click sql server agent -- Multi Server Administration -- Make this a master.
During this process you will be asked to create a MSX operator. and to enlist targets. the targets will need to be pre-registered with your master's instance and then define the jobs on the master and then you will be able to target multiple servers.
understand that this process is designed to return all job history to the master so you can check the progress of job operations from one place. however, just as with the highlander, there can be only one.... meaning that a target cannot be a master for other servers.
:confused: and dont forget to check books online,
BOOKS ONLINE {Multiserver Administration}
Wednesday, March 7, 2012
MS SQL 2005, .NET, logins/sec and page faults
Hi, all.
I would use Profiler to see what these clients are up to. If they are
generating tons of Audit:Login events, there is something fishy. Either
they don't use pooling, or misbehave so that pooling is cannot be used.
I think a common error is to fail to close the connections.
>
I would use Profiler to see what these clients are up to. If they are
generating tons of Audit:Login events, there is something fishy. Either
they don't use pooling, or misbehave so that pooling is cannot be used.
I think a common error is to fail to close the connections.
>
If on the other hand they generate a lot of sp_reset_connection, then
at least connection pooling is in order. (sp_reset_connection is
executed when a connection is reused from the pool.)
>
I just sampled all statements for one hour, and we had ~450.000 calls
to sp_reset_connection, or 125 calls per second. Seems way too high to
me, even if the documentation describes it as lightweight.
Al least connection pooling is working!
Yes, with that connection rate, he disconnected model is not very good.
Connection pooling is particular useful in things like web applications,
when you have many users that connect through the same middleware (the
web server), and that run queries very infrequently.
>
Al least connection pooling is working!
More or less.
We also have a tiny ASP app that writes one row to the db for each HTTP
request it receives. The ASP app used to use connection pools with
default settings. After changing Min and Max pool size to 300,
everything is suddenly more normal, now the server is so fast my
profiler traces has to be changed to make them report rows at all :-)
We have a couple of pathological sql servers that have lots and lots of
page faults per second, up to 4000. Our client programs are written in
C#/.NET 1.1 and utilizes connection pooling.
Some of the client programs seems to log in hundred of times per
second, as reported by perfmon->.SQLServer:General
Statistics->Logins/sec. Stopping the client programs reduces that
number significantly.
We've done code reviews of the client programs and they look OK.
Monitoring .NET connections&pools does not show anything suspicicous.
We're currently rewriting the clients to use one db connection instead
of the pools, but that takes some time and may introduce bugs. Does
anyone know why we have these problems and/or why logins/sec is so
high? I'm thinking "bugs in the .NET client", but really have no
idea...
One thought I had was that the Page Faults reported for sqlsrv.exe is
related to memory mapped IO and therefore can be ignored. Right or
wrong?
Any thoughs/pointers/ideas, even wild guesses, are most welcome.
Bjrn
PS: The server memory is fixed at 1.5GB out of 2GB physical ram,
clients run on the same machine and use TCP/IP comm.(I know...) The
host itself is not paging.bjorn.augestad@.gmail.com (bjorn.augestad@.gmail.com) writes:
Quote:
Originally Posted by
We have a couple of pathological sql servers that have lots and lots of
page faults per second, up to 4000. Our client programs are written in
C#/.NET 1.1 and utilizes connection pooling.
>
Some of the client programs seems to log in hundred of times per
second, as reported by perfmon->.SQLServer:General
Statistics->Logins/sec. Stopping the client programs reduces that
number significantly.
>
We've done code reviews of the client programs and they look OK.
Monitoring .NET connections&pools does not show anything suspicicous.
>
We're currently rewriting the clients to use one db connection instead
of the pools, but that takes some time and may introduce bugs. Does
anyone know why we have these problems and/or why logins/sec is so
high? I'm thinking "bugs in the .NET client", but really have no
idea...
I would use Profiler to see what these clients are up to. If they are
generating tons of Audit:Login events, there is something fishy. Either
they don't use pooling, or misbehave so that pooling is cannot be used.
I think a common error is to fail to close the connections.
If on the other hand they generate a lot of sp_reset_connection, then
at least connection pooling is in order. (sp_reset_connection is
executed when a connection is reused from the pool.)
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Erland Sommarskog wrote:
Quote:
Originally Posted by
bjorn.augestad@.gmail.com (bjorn.augestad@.gmail.com) writes:
Quote:
Originally Posted by
We have a couple of pathological sql servers that have lots and lots of
page faults per second, up to 4000. Our client programs are written in
C#/.NET 1.1 and utilizes connection pooling.
Some of the client programs seems to log in hundred of times per
second, as reported by perfmon->.SQLServer:General
Statistics->Logins/sec. Stopping the client programs reduces that
number significantly.
We've done code reviews of the client programs and they look OK.
Monitoring .NET connections&pools does not show anything suspicicous.
We're currently rewriting the clients to use one db connection instead
of the pools, but that takes some time and may introduce bugs. Does
anyone know why we have these problems and/or why logins/sec is so
high? I'm thinking "bugs in the .NET client", but really have no
idea...
>
I would use Profiler to see what these clients are up to. If they are
generating tons of Audit:Login events, there is something fishy. Either
they don't use pooling, or misbehave so that pooling is cannot be used.
I think a common error is to fail to close the connections.
>
If on the other hand they generate a lot of sp_reset_connection, then
at least connection pooling is in order. (sp_reset_connection is
executed when a connection is reused from the pool.)
>
I just sampled all statements for one hour, and we had ~450.000 calls
to sp_reset_connection, or 125 calls per second. Seems way too high to
me, even if the documentation describes it as lightweight.
I guess we'll continue to rewrite the clients to use just one
connection wherever possible. The changes made so far has improved the
situation a lot. :-)
Thanks.
Bjrn|||bjorn.augestad@.gmail.com (bjorn.augestad@.gmail.com) writes:
Quote:
Originally Posted by
I just sampled all statements for one hour, and we had ~450.000 calls
to sp_reset_connection, or 125 calls per second. Seems way too high to
me, even if the documentation describes it as lightweight.
Al least connection pooling is working!
Quote:
Originally Posted by
I guess we'll continue to rewrite the clients to use just one
connection wherever possible. The changes made so far has improved the
situation a lot. :-)
Yes, with that connection rate, he disconnected model is not very good.
Connection pooling is particular useful in things like web applications,
when you have many users that connect through the same middleware (the
web server), and that run queries very infrequently.
The model is usually fine for Windows applications too. But if you have some
service-type of thing which does not have to wait for a user that goes for a
coffee, it may be better to stay connected.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Erland Sommarskog wrote:
Quote:
Originally Posted by
bjorn.augestad@.gmail.com (bjorn.augestad@.gmail.com) writes:
Quote:
Originally Posted by
I just sampled all statements for one hour, and we had ~450.000 calls
to sp_reset_connection, or 125 calls per second. Seems way too high to
me, even if the documentation describes it as lightweight.
>
Al least connection pooling is working!
More or less.
We also have a tiny ASP app that writes one row to the db for each HTTP
request it receives. The ASP app used to use connection pools with
default settings. After changing Min and Max pool size to 300,
everything is suddenly more normal, now the server is so fast my
profiler traces has to be changed to make them report rows at all :-)
Stuff that used to take between 1200 and 7000ms now finishes in 1ms, so
I guess the problem has been solved.
Have a great weekend.
Bjrn
[snip]
Saturday, February 25, 2012
MS SQL 2000, 2005 multiple instances not broadcasted to other subnets
We currently have multiple instances of MS Sql 2000 and MS SQL 2005 installed on servers. When at other locations that uses different subnets only the default instance is available, published, broadcasted, selectable.
We have TCPIP and name pipes enabled for all instances. This seems to be a common problem for all locations.
As I understand your situation, you have the set of SQL server instances installed on some subnet. From a different subnet, your client application is trying to enumerate the list of SQL instances available. This is an inherit behavior of the SQL instance discovery mechanism. The client application uses User Datagram Protocol (UDP) to send a message on the broadcast address. Most of the hardware network routers available are designed to prevent routing of UDP messages on the broadcast address beyond the subnet of the sender. The end result is what you are seeing where SQL instances on a different subnet can not be discovered. You can still connect to them if you know the machine name and the instance name.
Jimmy
|||Jimmy thanks, that makes sense.Monday, February 20, 2012
MS Service Pack frustrations
I just have to vent. I just upgraded out production database to a pair of
clustered DL740 servers running Windows Server 2003 Enterprise Edition, SP1.
My SQL is 2000 with Service Pack4. The "new" items in this configuration are
the servers themselves, Server 2003, SP1 and SQL 2000 SP4.
My first gripe is with the Windodws 2000 SP1. Microsoft Windows Server 2003
Service Pack 1 (SP1) implements a security feature that reduces the size of
the queue for concurrent TCP/IP connections to the server. This is done
because the OS assumes a DoS attack is occuring. There is NO notification
that this event has happened in any event log. Do you suppose that
administrators might want to be notified if the OS thinks such an event is
occuring? Not only does this frost me, but I spent more than 8 hours over two
days on the phone with MS tech support and THEY DIDN'T EVEN FIND THE
SOLUTION!!! One of our developers searched KB articles and came up with
KB899599 which gave us our only clue to this issue. Once we implemented the
workaround, the problem was resolved. Meanwhile our customers experienced
dropped connections for three days.
My second gripe is with SQL 2000 SP4 and it's sudden lack of support for all
memory when using AWE. This little bit of fun is documented in KB899761.
Since both of these service packs were introduced in our new configuration,
you can imagine we had a fun time wading through all of this to get things
back to normal. I'm going back to my original stance that NOTHING from MS as
far as patches is worth putting on until they are at least 6 months old.
Thanks for letting me get on my soapbox.
Ken
As Microsoft says: Test everything in a Test environment before you put it
into production.
I work for a very large bank, and with this process, we have never burned
our fingers and are capable of rolling out a patch or fix to all servers
knowing that it works as desired, and usually quicker than someone without a
test environment.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"kmkrause2" <kmkrause2@.discussions.microsoft.com> wrote in message
news:9A825D91-B20E-40EC-843F-77AADFE9A0ED@.microsoft.com...
> I just have to vent. I just upgraded out production database to a pair of
> clustered DL740 servers running Windows Server 2003 Enterprise Edition,
> SP1.
> My SQL is 2000 with Service Pack4. The "new" items in this configuration
> are
> the servers themselves, Server 2003, SP1 and SQL 2000 SP4.
> My first gripe is with the Windodws 2000 SP1. Microsoft Windows Server
> 2003
> Service Pack 1 (SP1) implements a security feature that reduces the size
> of
> the queue for concurrent TCP/IP connections to the server. This is done
> because the OS assumes a DoS attack is occuring. There is NO notification
> that this event has happened in any event log. Do you suppose that
> administrators might want to be notified if the OS thinks such an event is
> occuring? Not only does this frost me, but I spent more than 8 hours over
> two
> days on the phone with MS tech support and THEY DIDN'T EVEN FIND THE
> SOLUTION!!! One of our developers searched KB articles and came up with
> KB899599 which gave us our only clue to this issue. Once we implemented
> the
> workaround, the problem was resolved. Meanwhile our customers experienced
> dropped connections for three days.
> My second gripe is with SQL 2000 SP4 and it's sudden lack of support for
> all
> memory when using AWE. This little bit of fun is documented in KB899761.
> Since both of these service packs were introduced in our new
> configuration,
> you can imagine we had a fun time wading through all of this to get things
> back to normal. I'm going back to my original stance that NOTHING from MS
> as
> far as patches is worth putting on until they are at least 6 months old.
> Thanks for letting me get on my soapbox.
> Ken
>
clustered DL740 servers running Windows Server 2003 Enterprise Edition, SP1.
My SQL is 2000 with Service Pack4. The "new" items in this configuration are
the servers themselves, Server 2003, SP1 and SQL 2000 SP4.
My first gripe is with the Windodws 2000 SP1. Microsoft Windows Server 2003
Service Pack 1 (SP1) implements a security feature that reduces the size of
the queue for concurrent TCP/IP connections to the server. This is done
because the OS assumes a DoS attack is occuring. There is NO notification
that this event has happened in any event log. Do you suppose that
administrators might want to be notified if the OS thinks such an event is
occuring? Not only does this frost me, but I spent more than 8 hours over two
days on the phone with MS tech support and THEY DIDN'T EVEN FIND THE
SOLUTION!!! One of our developers searched KB articles and came up with
KB899599 which gave us our only clue to this issue. Once we implemented the
workaround, the problem was resolved. Meanwhile our customers experienced
dropped connections for three days.
My second gripe is with SQL 2000 SP4 and it's sudden lack of support for all
memory when using AWE. This little bit of fun is documented in KB899761.
Since both of these service packs were introduced in our new configuration,
you can imagine we had a fun time wading through all of this to get things
back to normal. I'm going back to my original stance that NOTHING from MS as
far as patches is worth putting on until they are at least 6 months old.
Thanks for letting me get on my soapbox.
Ken
As Microsoft says: Test everything in a Test environment before you put it
into production.
I work for a very large bank, and with this process, we have never burned
our fingers and are capable of rolling out a patch or fix to all servers
knowing that it works as desired, and usually quicker than someone without a
test environment.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"kmkrause2" <kmkrause2@.discussions.microsoft.com> wrote in message
news:9A825D91-B20E-40EC-843F-77AADFE9A0ED@.microsoft.com...
> I just have to vent. I just upgraded out production database to a pair of
> clustered DL740 servers running Windows Server 2003 Enterprise Edition,
> SP1.
> My SQL is 2000 with Service Pack4. The "new" items in this configuration
> are
> the servers themselves, Server 2003, SP1 and SQL 2000 SP4.
> My first gripe is with the Windodws 2000 SP1. Microsoft Windows Server
> 2003
> Service Pack 1 (SP1) implements a security feature that reduces the size
> of
> the queue for concurrent TCP/IP connections to the server. This is done
> because the OS assumes a DoS attack is occuring. There is NO notification
> that this event has happened in any event log. Do you suppose that
> administrators might want to be notified if the OS thinks such an event is
> occuring? Not only does this frost me, but I spent more than 8 hours over
> two
> days on the phone with MS tech support and THEY DIDN'T EVEN FIND THE
> SOLUTION!!! One of our developers searched KB articles and came up with
> KB899599 which gave us our only clue to this issue. Once we implemented
> the
> workaround, the problem was resolved. Meanwhile our customers experienced
> dropped connections for three days.
> My second gripe is with SQL 2000 SP4 and it's sudden lack of support for
> all
> memory when using AWE. This little bit of fun is documented in KB899761.
> Since both of these service packs were introduced in our new
> configuration,
> you can imagine we had a fun time wading through all of this to get things
> back to normal. I'm going back to my original stance that NOTHING from MS
> as
> far as patches is worth putting on until they are at least 6 months old.
> Thanks for letting me get on my soapbox.
> Ken
>
MS Service Pack frustrations
I just have to vent. I just upgraded out production database to a pair of
clustered DL740 servers running Windows Server 2003 Enterprise Edition, SP1.
My SQL is 2000 with Service Pack4. The "new" items in this configuration are
the servers themselves, Server 2003, SP1 and SQL 2000 SP4.
My first gripe is with the Windodws 2000 SP1. Microsoft Windows Server 2003
Service Pack 1 (SP1) implements a security feature that reduces the size of
the queue for concurrent TCP/IP connections to the server. This is done
because the OS assumes a DoS attack is occuring. There is NO notification
that this event has happened in any event log. Do you suppose that
administrators might want to be notified if the OS thinks such an event is
occuring? Not only does this frost me, but I spent more than 8 hours over tw
o
days on the phone with MS tech support and THEY DIDN'T EVEN FIND THE
SOLUTION!!! One of our developers searched KB articles and came up with
KB899599 which gave us our only clue to this issue. Once we implemented the
workaround, the problem was resolved. Meanwhile our customers experienced
dropped connections for three days.
My second gripe is with SQL 2000 SP4 and it's sudden lack of support for all
memory when using AWE. This little bit of fun is documented in KB899761.
Since both of these service packs were introduced in our new configuration,
you can imagine we had a fun time wading through all of this to get things
back to normal. I'm going back to my original stance that NOTHING from MS as
far as patches is worth putting on until they are at least 6 months old.
Thanks for letting me get on my soapbox.
KenAs Microsoft says: Test everything in a Test environment before you put it
into production.
I work for a very large bank, and with this process, we have never burned
our fingers and are capable of rolling out a patch or fix to all servers
knowing that it works as desired, and usually quicker than someone without a
test environment.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"kmkrause2" <kmkrause2@.discussions.microsoft.com> wrote in message
news:9A825D91-B20E-40EC-843F-77AADFE9A0ED@.microsoft.com...
> I just have to vent. I just upgraded out production database to a pair of
> clustered DL740 servers running Windows Server 2003 Enterprise Edition,
> SP1.
> My SQL is 2000 with Service Pack4. The "new" items in this configuration
> are
> the servers themselves, Server 2003, SP1 and SQL 2000 SP4.
> My first gripe is with the Windodws 2000 SP1. Microsoft Windows Server
> 2003
> Service Pack 1 (SP1) implements a security feature that reduces the size
> of
> the queue for concurrent TCP/IP connections to the server. This is done
> because the OS assumes a DoS attack is occuring. There is NO notification
> that this event has happened in any event log. Do you suppose that
> administrators might want to be notified if the OS thinks such an event is
> occuring? Not only does this frost me, but I spent more than 8 hours over
> two
> days on the phone with MS tech support and THEY DIDN'T EVEN FIND THE
> SOLUTION!!! One of our developers searched KB articles and came up with
> KB899599 which gave us our only clue to this issue. Once we implemented
> the
> workaround, the problem was resolved. Meanwhile our customers experienced
> dropped connections for three days.
> My second gripe is with SQL 2000 SP4 and it's sudden lack of support for
> all
> memory when using AWE. This little bit of fun is documented in KB899761.
> Since both of these service packs were introduced in our new
> configuration,
> you can imagine we had a fun time wading through all of this to get things
> back to normal. I'm going back to my original stance that NOTHING from MS
> as
> far as patches is worth putting on until they are at least 6 months old.
> Thanks for letting me get on my soapbox.
> Ken
>
clustered DL740 servers running Windows Server 2003 Enterprise Edition, SP1.
My SQL is 2000 with Service Pack4. The "new" items in this configuration are
the servers themselves, Server 2003, SP1 and SQL 2000 SP4.
My first gripe is with the Windodws 2000 SP1. Microsoft Windows Server 2003
Service Pack 1 (SP1) implements a security feature that reduces the size of
the queue for concurrent TCP/IP connections to the server. This is done
because the OS assumes a DoS attack is occuring. There is NO notification
that this event has happened in any event log. Do you suppose that
administrators might want to be notified if the OS thinks such an event is
occuring? Not only does this frost me, but I spent more than 8 hours over tw
o
days on the phone with MS tech support and THEY DIDN'T EVEN FIND THE
SOLUTION!!! One of our developers searched KB articles and came up with
KB899599 which gave us our only clue to this issue. Once we implemented the
workaround, the problem was resolved. Meanwhile our customers experienced
dropped connections for three days.
My second gripe is with SQL 2000 SP4 and it's sudden lack of support for all
memory when using AWE. This little bit of fun is documented in KB899761.
Since both of these service packs were introduced in our new configuration,
you can imagine we had a fun time wading through all of this to get things
back to normal. I'm going back to my original stance that NOTHING from MS as
far as patches is worth putting on until they are at least 6 months old.
Thanks for letting me get on my soapbox.
KenAs Microsoft says: Test everything in a Test environment before you put it
into production.
I work for a very large bank, and with this process, we have never burned
our fingers and are capable of rolling out a patch or fix to all servers
knowing that it works as desired, and usually quicker than someone without a
test environment.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"kmkrause2" <kmkrause2@.discussions.microsoft.com> wrote in message
news:9A825D91-B20E-40EC-843F-77AADFE9A0ED@.microsoft.com...
> I just have to vent. I just upgraded out production database to a pair of
> clustered DL740 servers running Windows Server 2003 Enterprise Edition,
> SP1.
> My SQL is 2000 with Service Pack4. The "new" items in this configuration
> are
> the servers themselves, Server 2003, SP1 and SQL 2000 SP4.
> My first gripe is with the Windodws 2000 SP1. Microsoft Windows Server
> 2003
> Service Pack 1 (SP1) implements a security feature that reduces the size
> of
> the queue for concurrent TCP/IP connections to the server. This is done
> because the OS assumes a DoS attack is occuring. There is NO notification
> that this event has happened in any event log. Do you suppose that
> administrators might want to be notified if the OS thinks such an event is
> occuring? Not only does this frost me, but I spent more than 8 hours over
> two
> days on the phone with MS tech support and THEY DIDN'T EVEN FIND THE
> SOLUTION!!! One of our developers searched KB articles and came up with
> KB899599 which gave us our only clue to this issue. Once we implemented
> the
> workaround, the problem was resolved. Meanwhile our customers experienced
> dropped connections for three days.
> My second gripe is with SQL 2000 SP4 and it's sudden lack of support for
> all
> memory when using AWE. This little bit of fun is documented in KB899761.
> Since both of these service packs were introduced in our new
> configuration,
> you can imagine we had a fun time wading through all of this to get things
> back to normal. I'm going back to my original stance that NOTHING from MS
> as
> far as patches is worth putting on until they are at least 6 months old.
> Thanks for letting me get on my soapbox.
> Ken
>
MS Service Pack frustrations
I just have to vent. I just upgraded out production database to a pair of
clustered DL740 servers running Windows Server 2003 Enterprise Edition, SP1.
My SQL is 2000 with Service Pack4. The "new" items in this configuration are
the servers themselves, Server 2003, SP1 and SQL 2000 SP4.
My first gripe is with the Windodws 2000 SP1. Microsoft Windows Server 2003
Service Pack 1 (SP1) implements a security feature that reduces the size of
the queue for concurrent TCP/IP connections to the server. This is done
because the OS assumes a DoS attack is occuring. There is NO notification
that this event has happened in any event log. Do you suppose that
administrators might want to be notified if the OS thinks such an event is
occuring? Not only does this frost me, but I spent more than 8 hours over two
days on the phone with MS tech support and THEY DIDN'T EVEN FIND THE
SOLUTION!!! One of our developers searched KB articles and came up with
KB899599 which gave us our only clue to this issue. Once we implemented the
workaround, the problem was resolved. Meanwhile our customers experienced
dropped connections for three days.
My second gripe is with SQL 2000 SP4 and it's sudden lack of support for all
memory when using AWE. This little bit of fun is documented in KB899761.
Since both of these service packs were introduced in our new configuration,
you can imagine we had a fun time wading through all of this to get things
back to normal. I'm going back to my original stance that NOTHING from MS as
far as patches is worth putting on until they are at least 6 months old.
Thanks for letting me get on my soapbox.
KenAs Microsoft says: Test everything in a Test environment before you put it
into production.
I work for a very large bank, and with this process, we have never burned
our fingers and are capable of rolling out a patch or fix to all servers
knowing that it works as desired, and usually quicker than someone without a
test environment.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"kmkrause2" <kmkrause2@.discussions.microsoft.com> wrote in message
news:9A825D91-B20E-40EC-843F-77AADFE9A0ED@.microsoft.com...
> I just have to vent. I just upgraded out production database to a pair of
> clustered DL740 servers running Windows Server 2003 Enterprise Edition,
> SP1.
> My SQL is 2000 with Service Pack4. The "new" items in this configuration
> are
> the servers themselves, Server 2003, SP1 and SQL 2000 SP4.
> My first gripe is with the Windodws 2000 SP1. Microsoft Windows Server
> 2003
> Service Pack 1 (SP1) implements a security feature that reduces the size
> of
> the queue for concurrent TCP/IP connections to the server. This is done
> because the OS assumes a DoS attack is occuring. There is NO notification
> that this event has happened in any event log. Do you suppose that
> administrators might want to be notified if the OS thinks such an event is
> occuring? Not only does this frost me, but I spent more than 8 hours over
> two
> days on the phone with MS tech support and THEY DIDN'T EVEN FIND THE
> SOLUTION!!! One of our developers searched KB articles and came up with
> KB899599 which gave us our only clue to this issue. Once we implemented
> the
> workaround, the problem was resolved. Meanwhile our customers experienced
> dropped connections for three days.
> My second gripe is with SQL 2000 SP4 and it's sudden lack of support for
> all
> memory when using AWE. This little bit of fun is documented in KB899761.
> Since both of these service packs were introduced in our new
> configuration,
> you can imagine we had a fun time wading through all of this to get things
> back to normal. I'm going back to my original stance that NOTHING from MS
> as
> far as patches is worth putting on until they are at least 6 months old.
> Thanks for letting me get on my soapbox.
> Ken
>
clustered DL740 servers running Windows Server 2003 Enterprise Edition, SP1.
My SQL is 2000 with Service Pack4. The "new" items in this configuration are
the servers themselves, Server 2003, SP1 and SQL 2000 SP4.
My first gripe is with the Windodws 2000 SP1. Microsoft Windows Server 2003
Service Pack 1 (SP1) implements a security feature that reduces the size of
the queue for concurrent TCP/IP connections to the server. This is done
because the OS assumes a DoS attack is occuring. There is NO notification
that this event has happened in any event log. Do you suppose that
administrators might want to be notified if the OS thinks such an event is
occuring? Not only does this frost me, but I spent more than 8 hours over two
days on the phone with MS tech support and THEY DIDN'T EVEN FIND THE
SOLUTION!!! One of our developers searched KB articles and came up with
KB899599 which gave us our only clue to this issue. Once we implemented the
workaround, the problem was resolved. Meanwhile our customers experienced
dropped connections for three days.
My second gripe is with SQL 2000 SP4 and it's sudden lack of support for all
memory when using AWE. This little bit of fun is documented in KB899761.
Since both of these service packs were introduced in our new configuration,
you can imagine we had a fun time wading through all of this to get things
back to normal. I'm going back to my original stance that NOTHING from MS as
far as patches is worth putting on until they are at least 6 months old.
Thanks for letting me get on my soapbox.
KenAs Microsoft says: Test everything in a Test environment before you put it
into production.
I work for a very large bank, and with this process, we have never burned
our fingers and are capable of rolling out a patch or fix to all servers
knowing that it works as desired, and usually quicker than someone without a
test environment.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"kmkrause2" <kmkrause2@.discussions.microsoft.com> wrote in message
news:9A825D91-B20E-40EC-843F-77AADFE9A0ED@.microsoft.com...
> I just have to vent. I just upgraded out production database to a pair of
> clustered DL740 servers running Windows Server 2003 Enterprise Edition,
> SP1.
> My SQL is 2000 with Service Pack4. The "new" items in this configuration
> are
> the servers themselves, Server 2003, SP1 and SQL 2000 SP4.
> My first gripe is with the Windodws 2000 SP1. Microsoft Windows Server
> 2003
> Service Pack 1 (SP1) implements a security feature that reduces the size
> of
> the queue for concurrent TCP/IP connections to the server. This is done
> because the OS assumes a DoS attack is occuring. There is NO notification
> that this event has happened in any event log. Do you suppose that
> administrators might want to be notified if the OS thinks such an event is
> occuring? Not only does this frost me, but I spent more than 8 hours over
> two
> days on the phone with MS tech support and THEY DIDN'T EVEN FIND THE
> SOLUTION!!! One of our developers searched KB articles and came up with
> KB899599 which gave us our only clue to this issue. Once we implemented
> the
> workaround, the problem was resolved. Meanwhile our customers experienced
> dropped connections for three days.
> My second gripe is with SQL 2000 SP4 and it's sudden lack of support for
> all
> memory when using AWE. This little bit of fun is documented in KB899761.
> Since both of these service packs were introduced in our new
> configuration,
> you can imagine we had a fun time wading through all of this to get things
> back to normal. I'm going back to my original stance that NOTHING from MS
> as
> far as patches is worth putting on until they are at least 6 months old.
> Thanks for letting me get on my soapbox.
> Ken
>
MS Security patch MS03-031
I am trying to install ms03-031 (q815495) on a couple of our sql servers and
get the following error message:
'No sql server instances installed on this computer qualify for this Hotfix.
Check the version, language and
service pack requirement for this Hotfix', and the patch does not go on. I h
ave successfully put this fix
onto 35 other SQL Server 2000 SP3 servers.
The two I am getting the errors on are SQL Server 2000, sp3, and the languag
e is English. I cant seem to find
any log files to point me any Further. Would appreciate any suggestions, thi
ngs to check, etc. to find why we are getting
this error. Thanks, Johnlogfiles are put in c:\%windows%\sqlhotfix
Kevin Connell, MCDBA
----
The views expressed here are my own
and not of my employer.
----
"John Anthony" <anonymous@.discussions.microsoft.com> wrote in message
news:EB38C53E-02C2-4E78-88EB-9D915FC06975@.microsoft.com...
and get the following error message:
Hotfix. Check the version, language and
have successfully put this fix
language is English. I cant seem to find
things to check, etc. to find why we are getting
Here is the tail end, where the error occurs.
Im not sure what it is saying. We are running SQL Server 2000 SE, product ve
rsion 8.00.760(sp3).
First error seems to be a product code issue. Any suggestions on how to fix
or what to do next
would be gratly appreciated. thanks, John.
<Func Name='CService::~CService'><Func Name='GetProductCodeForInstance'><End
Func Name='GetProductCodeForInstance' Return='2' GetLastError='997'><EndFunc
Name='PerformSQLDetection' Return='0' GetLastError='997'><Func Name='Qualif
ySQLComputer'><Func Name='Q
ualifySQLInstance'>
Verifying Instance MSSQLSERVER to see if it qualifies for this hotfix
Instance MSSQLSERVER does not meet the requirements for this HotFix or there
is no such instance installed on this computer
<EndFunc Name='QualifySQLInstance' Return='87' GetLastError='997'>
HotFix Installer did not find any installation or instance of SQL that quali
fies for this hotfix
<EndFunc Name='QualifySQLComputer' Return='1168' GetLastError='997'>
No components of SQL found on this computer that qualifies for this package.
<EndFunc Name='SQLHotfix' Return='1168' GetLastError='997'><EndFunc Name='Ha
ndlePackage' Return='1168' GetLastError='997'>
And:
Verifying Instance MSSQLSERVER to see if it qualifies for this hotfix
Instance MSSQLSERVER does not meet the requirements for this HotFix or there
is no such instance installed on this computer
<EndFunc Name='QualifySQLInstance' Return='87' GetLastError='997'>
HotFix Installer did not find any installation or instance of SQL that quali
fies for this hotfix
<EndFunc Name='QualifySQLComputer' Return='1168' GetLastError='997'>
No components of SQL found on this computer that qualifies for this package.
<EndFunc Name='SQLHotfix' Return='1168' GetLastError='997'><EndFunc Name='Ha
ndlePackage' Return='1168' GetLastError='997'>
=== Completed processing package defined in Hotfix2.inf with return code: 11
68
=== Of the 2 packages no package qualified to run on this computer
<EndFunc Name='ProcessPackages' Return='1168' GetLastError='1813'><EndFunc N
ame='WinMain' Return='1168' GetLastError='1813'>|||Have you run SQLDiag.exe on the machines that are having problems and
reviewed the output of SQLdiag.txt?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Reviewed output of SQLDiag.txt and nothing stands out. Compared with other S
P3 systems, and everything seems the
same. Could you please advise what to do next, Thanks, John|||Attach the SQLdiag.txt . I'd like to take a look.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
Here is the output of the hot fix. I cant seem to attach the sqldiag.txt her
e. Can I email it? Thanks for looking at this.
John.
Microsoft SQL Server Group of Products HotFix beginning Mon Dec 08 13:40:43
2003
<Func Name='WinMain'><Func Name='InitGlobals'>
OS Detected: Windows 2000 family
<EndFunc Name='InitGlobals' Return='0' GetLastError='203'><Func Name='Proces
sPackages'><Func Name='LoadPackages'><Func Name='ReadPackageInformation'><En
dFunc Name='ReadPackageInformation' Return='0' GetLastError='0'><Func Name='
ReadTargetProductInformatio
n'><EndFunc Name='ReadTargetProductInformation' Return='0' GetLastError='0'>
<Func Name='ReadPackageInformation'><EndFunc Name='ReadPackageInformation' R
eturn='0' GetLastError='0'><Func Name='ReadTargetProductInformation'><EndFun
c Name='ReadTargetProductIn
formation' Return='0' GetLastError='0'><EndFunc Name='LoadPackages' Return='
0' GetLastError='2'>
=== Processing package defined in Hotfix1.inf
<Func Name='HandlePackage'>
=== PACKAGE INFORMATION
=== Starting Hotfix Build : 0818
=== Hotfix KB Article : 815495
=== Installer Base: Hotfix
=== TARGET PRODUCT FOR THIS HOTFIX (Requirements)
=== Target Product Name : SQL
=== Target Product Version : 8.00
=== Target Product Service Pack requirement : 3
<Func Name='SQLHotfix'>
=== Hotfix targetting SQL Installations
<Func Name='PerformSQLDetection'><Func Name='CService::CService'><Func Name=
'CServiceNT::CServiceNT'><Func Name='CServiceNT::Open'><EndFunc Name='CServi
ceNT::Open' Return='T' GetLastError='997'><Func Name='CServiceNT::UpdateServ
iceStatus'><Func Name='CSer
viceNT::~CServiceNT'><Func Name='CServiceNT::Close'><EndFunc Name='CServiceN
T::Close' Return='T' GetLastError='997'><Func Name='CService::~CService'><Fu
nc Name='CService::CService'><Func Name='CServiceNT::CServiceNT'><Func Name=
'CServiceNT::Open'><EndFunc
Name='CServiceNT::Open' Return='T' GetLastError='997'><Func Name='CServiceNT
::UpdateServiceStatus'><Func Name='CServiceNT::~CServiceNT'><Func Name='CSer
viceNT::Close'><EndFunc Name='CServiceNT::Close' Return='T' GetLastError='99
7'><Func Name='CService::~
CService'><Func Name='GetProductCodeForInstance'><EndFunc Name='GetProductCo
deForInstance' Return='2' GetLastError='997'><EndFunc Name='PerformSQLDetect
ion' Return='0' GetLastError='997'><Func Name='CorrectCSDVersion'><EndFunc N
ame='CorrectCSDVersion' Ret
urn='0' GetLastError='0'><Func Name='PerformSQLDetection'><Func Name='CServi
ce::CService'><Func Name='CServiceNT::CServiceNT'><Func Name='CServiceNT::Op
en'><EndFunc Name='CServiceNT::Open' Return='T' GetLastError='997'><Func Nam
e='CServiceNT::UpdateServic
eStatus'><Func Name='CServiceNT::~CServiceNT'><Func Name='CServiceNT::Close'
><EndFunc Name='CServiceNT::Close' Return='T' GetLastError='997'><Func Name=
'CService::~CService'><Func Name='CService::CService'><Func Name='CServiceNT
::CServiceNT'><Func Name='C
ServiceNT::Open'><EndFunc Name='CServiceNT::Open' Return='T' GetLastError='9
97'><Func Name='CServiceNT::UpdateServiceStatus'><Func Name='CServiceNT::~CS
erviceNT'><Func Name='CServiceNT::Close'><EndFunc Name='CServiceNT::Close' R
eturn='T' GetLastError='997
'><Func Name='CService::~CService'><Func Name='GetProductCodeForInstance'><E
ndFunc Name='GetProductCodeForInstance' Return='2' GetLastError='997'><EndFu
nc Name='PerformSQLDetection' Return='0' GetLastError='997'><Func Name='Qual
ifySQLComputer'><Func Name=
'QualifySQLInstance'>
Verifying Instance MSSQLSERVER to see if it qualifies for this hotfix
Instance MSSQLSERVER does not meet the requirements for this HotFix or there
is no such instance installed on this computer
<EndFunc Name='QualifySQLInstance' Return='87' GetLastError='997'>
HotFix Installer did not find any installation or instance of SQL that quali
fies for this hotfix
<EndFunc Name='QualifySQLComputer' Return='1168' GetLastError='997'>
No components of SQL found on this computer that qualifies for this package.
<EndFunc Name='SQLHotfix' Return='1168' GetLastError='997'><EndFunc Name='Ha
ndlePackage' Return='1168' GetLastError='997'>
=== Completed processing package defined in Hotfix1.inf with return code: 11
68
=== Processing package defined in Hotfix2.inf
<Func Name='HandlePackage'>
=== PACKAGE INFORMATION
=== Starting Hotfix Build : 0818
=== Hotfix KB Article : 815495
=== Installer Base: Hotfix
=== TARGET PRODUCT FOR THIS HOTFIX (Requirements)
=== Target Product Name : SQL
=== Target Product Version : 8.00
=== Target Product Service Pack requirement : None
<Func Name='SQLHotfix'>
=== Hotfix targetting SQL Installations
<Func Name='PerformSQLDetection'><Func Name='CService::CService'><Func Name=
'CServiceNT::CServiceNT'><Func Name='CServiceNT::Open'><EndFunc Name='CServi
ceNT::Open' Return='T' GetLastError='997'><Func Name='CServiceNT::UpdateServ
iceStatus'><Func Name='CSer
viceNT::~CServiceNT'><Func Name='CServiceNT::Close'><EndFunc Name='CServiceN
T::Close' Return='T' GetLastError='997'><Func Name='CService::~CService'><Fu
nc Name='CService::CService'><Func Name='CServiceNT::CServiceNT'><Func Name=
'CServiceNT::Open'><EndFunc
Name='CServiceNT::Open' Return='T' GetLastError='997'><Func Name='CServiceNT
::UpdateServiceStatus'><Func Name='CServiceNT::~CServiceNT'><Func Name='CSer
viceNT::Close'><EndFunc Name='CServiceNT::Close' Return='T' GetLastError='99
7'><Func Name='CService::~
CService'><Func Name='GetProductCodeForInstance'><EndFunc Name='GetProductCo
deForInstance' Return='2' GetLastError='997'><EndFunc Name='PerformSQLDetect
ion' Return='0' GetLastError='997'><Func Name='CorrectCSDVersion'><EndFunc N
ame='CorrectCSDVersion' Ret
urn='0' GetLastError='0'><Func Name='PerformSQLDetection'><Func Name='CServi
ce::CService'><Func Name='CServiceNT::CServiceNT'><Func Name='CServiceNT::Op
en'><EndFunc Name='CServiceNT::Open' Return='T' GetLastError='997'><Func Nam
e='CServiceNT::UpdateServic
eStatus'><Func Name='CServiceNT::~CServiceNT'><Func Name='CServiceNT::Close'
><EndFunc Name='CServiceNT::Close' Return='T' GetLastError='997'><Func Name=
'CService::~CService'><Func Name='CService::CService'><Func Name='CServiceNT
::CServiceNT'><Func Name='C
ServiceNT::Open'><EndFunc Name='CServiceNT::Open' Return='T' GetLastError='9
97'><Func Name='CServiceNT::UpdateServiceStatus'><Func Name='CServiceNT::~CS
erviceNT'><Func Name='CServiceNT::Close'><EndFunc Name='CServiceNT::Close' R
eturn='T' GetLastError='997
'><Func Name='CService::~CService'><Func Name='GetProductCodeForInstance'><E
ndFunc Name='GetProductCodeForInstance' Return='2' GetLastError='997'><EndFu
nc Name='PerformSQLDetection' Return='0' GetLastError='997'><Func Name='Qual
ifySQLComputer'><Func Name=
'QualifySQLInstance'>
Verifying Instance MSSQLSERVER to see if it qualifies for this hotfix
Instance MSSQLSERVER does not meet the requirements for this HotFix or there
is no such instance installed on this computer
<EndFunc Name='QualifySQLInstance' Return='87' GetLastError='997'>
HotFix Installer did not find any installation or instance of SQL that quali
fies for this hotfix
<EndFunc Name='QualifySQLComputer' Return='1168' GetLastError='997'>
No components of SQL found on this computer that qualifies for this package.
<EndFunc Name='SQLHotfix' Return='1168' GetLastError='997'><EndFunc Name='Ha
ndlePackage' Return='1168' GetLastError='997'>
=== Completed processing package defined in Hotfix2.inf with return code: 11
68
=== Of the 2 packages no package qualified to run on this computer
<EndFunc Name='ProcessPackages' Return='1168' GetLastError='1813'><EndFunc N
ame='WinMain' Return='1168' GetLastError='1813'>|||Run the following command and post the results.
OSQL -E -Q"select @.@.version"
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Here is the output from the command. Thanks, John
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copy
right (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows N
T 5.0 (Build 2195: Service Pack 3)|||Review the following registry keys on your machine.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\CurrentVersion
\CSDVersion
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\CurrentVersion
\CSDVersionNumber
They should look like this:
CSDVersion (string) 8.00.761
CSDVersionNumber (dword) 300 (hex)
Update these keys as needed, and retry applying the Security Update.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
get the following error message:
'No sql server instances installed on this computer qualify for this Hotfix.
Check the version, language and
service pack requirement for this Hotfix', and the patch does not go on. I h
ave successfully put this fix
onto 35 other SQL Server 2000 SP3 servers.
The two I am getting the errors on are SQL Server 2000, sp3, and the languag
e is English. I cant seem to find
any log files to point me any Further. Would appreciate any suggestions, thi
ngs to check, etc. to find why we are getting
this error. Thanks, Johnlogfiles are put in c:\%windows%\sqlhotfix
Kevin Connell, MCDBA
----
The views expressed here are my own
and not of my employer.
----
"John Anthony" <anonymous@.discussions.microsoft.com> wrote in message
news:EB38C53E-02C2-4E78-88EB-9D915FC06975@.microsoft.com...
quote:
> I am trying to install ms03-031 (q815495) on a couple of our sql servers
and get the following error message:
quote:
> 'No sql server instances installed on this computer qualify for this
Hotfix. Check the version, language and
quote:
> service pack requirement for this Hotfix', and the patch does not go on. I
have successfully put this fix
quote:
> onto 35 other SQL Server 2000 SP3 servers.
> The two I am getting the errors on are SQL Server 2000, sp3, and the
language is English. I cant seem to find
quote:
> any log files to point me any Further. Would appreciate any suggestions,
things to check, etc. to find why we are getting
quote:|||Thanks, found the log files.
> this error. Thanks, John
Here is the tail end, where the error occurs.
Im not sure what it is saying. We are running SQL Server 2000 SE, product ve
rsion 8.00.760(sp3).
First error seems to be a product code issue. Any suggestions on how to fix
or what to do next
would be gratly appreciated. thanks, John.
<Func Name='CService::~CService'><Func Name='GetProductCodeForInstance'><End
Func Name='GetProductCodeForInstance' Return='2' GetLastError='997'><EndFunc
Name='PerformSQLDetection' Return='0' GetLastError='997'><Func Name='Qualif
ySQLComputer'><Func Name='Q
ualifySQLInstance'>
Verifying Instance MSSQLSERVER to see if it qualifies for this hotfix
Instance MSSQLSERVER does not meet the requirements for this HotFix or there
is no such instance installed on this computer
<EndFunc Name='QualifySQLInstance' Return='87' GetLastError='997'>
HotFix Installer did not find any installation or instance of SQL that quali
fies for this hotfix
<EndFunc Name='QualifySQLComputer' Return='1168' GetLastError='997'>
No components of SQL found on this computer that qualifies for this package.
<EndFunc Name='SQLHotfix' Return='1168' GetLastError='997'><EndFunc Name='Ha
ndlePackage' Return='1168' GetLastError='997'>
And:
Verifying Instance MSSQLSERVER to see if it qualifies for this hotfix
Instance MSSQLSERVER does not meet the requirements for this HotFix or there
is no such instance installed on this computer
<EndFunc Name='QualifySQLInstance' Return='87' GetLastError='997'>
HotFix Installer did not find any installation or instance of SQL that quali
fies for this hotfix
<EndFunc Name='QualifySQLComputer' Return='1168' GetLastError='997'>
No components of SQL found on this computer that qualifies for this package.
<EndFunc Name='SQLHotfix' Return='1168' GetLastError='997'><EndFunc Name='Ha
ndlePackage' Return='1168' GetLastError='997'>
=== Completed processing package defined in Hotfix2.inf with return code: 11
68
=== Of the 2 packages no package qualified to run on this computer
<EndFunc Name='ProcessPackages' Return='1168' GetLastError='1813'><EndFunc N
ame='WinMain' Return='1168' GetLastError='1813'>|||Have you run SQLDiag.exe on the machines that are having problems and
reviewed the output of SQLdiag.txt?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Reviewed output of SQLDiag.txt and nothing stands out. Compared with other S
P3 systems, and everything seems the
same. Could you please advise what to do next, Thanks, John|||Attach the SQLdiag.txt . I'd like to take a look.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
Here is the output of the hot fix. I cant seem to attach the sqldiag.txt her
e. Can I email it? Thanks for looking at this.
John.
Microsoft SQL Server Group of Products HotFix beginning Mon Dec 08 13:40:43
2003
<Func Name='WinMain'><Func Name='InitGlobals'>
OS Detected: Windows 2000 family
<EndFunc Name='InitGlobals' Return='0' GetLastError='203'><Func Name='Proces
sPackages'><Func Name='LoadPackages'><Func Name='ReadPackageInformation'><En
dFunc Name='ReadPackageInformation' Return='0' GetLastError='0'><Func Name='
ReadTargetProductInformatio
n'><EndFunc Name='ReadTargetProductInformation' Return='0' GetLastError='0'>
<Func Name='ReadPackageInformation'><EndFunc Name='ReadPackageInformation' R
eturn='0' GetLastError='0'><Func Name='ReadTargetProductInformation'><EndFun
c Name='ReadTargetProductIn
formation' Return='0' GetLastError='0'><EndFunc Name='LoadPackages' Return='
0' GetLastError='2'>
=== Processing package defined in Hotfix1.inf
<Func Name='HandlePackage'>
=== PACKAGE INFORMATION
=== Starting Hotfix Build : 0818
=== Hotfix KB Article : 815495
=== Installer Base: Hotfix
=== TARGET PRODUCT FOR THIS HOTFIX (Requirements)
=== Target Product Name : SQL
=== Target Product Version : 8.00
=== Target Product Service Pack requirement : 3
<Func Name='SQLHotfix'>
=== Hotfix targetting SQL Installations
<Func Name='PerformSQLDetection'><Func Name='CService::CService'><Func Name=
'CServiceNT::CServiceNT'><Func Name='CServiceNT::Open'><EndFunc Name='CServi
ceNT::Open' Return='T' GetLastError='997'><Func Name='CServiceNT::UpdateServ
iceStatus'><Func Name='CSer
viceNT::~CServiceNT'><Func Name='CServiceNT::Close'><EndFunc Name='CServiceN
T::Close' Return='T' GetLastError='997'><Func Name='CService::~CService'><Fu
nc Name='CService::CService'><Func Name='CServiceNT::CServiceNT'><Func Name=
'CServiceNT::Open'><EndFunc
Name='CServiceNT::Open' Return='T' GetLastError='997'><Func Name='CServiceNT
::UpdateServiceStatus'><Func Name='CServiceNT::~CServiceNT'><Func Name='CSer
viceNT::Close'><EndFunc Name='CServiceNT::Close' Return='T' GetLastError='99
7'><Func Name='CService::~
CService'><Func Name='GetProductCodeForInstance'><EndFunc Name='GetProductCo
deForInstance' Return='2' GetLastError='997'><EndFunc Name='PerformSQLDetect
ion' Return='0' GetLastError='997'><Func Name='CorrectCSDVersion'><EndFunc N
ame='CorrectCSDVersion' Ret
urn='0' GetLastError='0'><Func Name='PerformSQLDetection'><Func Name='CServi
ce::CService'><Func Name='CServiceNT::CServiceNT'><Func Name='CServiceNT::Op
en'><EndFunc Name='CServiceNT::Open' Return='T' GetLastError='997'><Func Nam
e='CServiceNT::UpdateServic
eStatus'><Func Name='CServiceNT::~CServiceNT'><Func Name='CServiceNT::Close'
><EndFunc Name='CServiceNT::Close' Return='T' GetLastError='997'><Func Name=
'CService::~CService'><Func Name='CService::CService'><Func Name='CServiceNT
::CServiceNT'><Func Name='C
ServiceNT::Open'><EndFunc Name='CServiceNT::Open' Return='T' GetLastError='9
97'><Func Name='CServiceNT::UpdateServiceStatus'><Func Name='CServiceNT::~CS
erviceNT'><Func Name='CServiceNT::Close'><EndFunc Name='CServiceNT::Close' R
eturn='T' GetLastError='997
'><Func Name='CService::~CService'><Func Name='GetProductCodeForInstance'><E
ndFunc Name='GetProductCodeForInstance' Return='2' GetLastError='997'><EndFu
nc Name='PerformSQLDetection' Return='0' GetLastError='997'><Func Name='Qual
ifySQLComputer'><Func Name=
'QualifySQLInstance'>
Verifying Instance MSSQLSERVER to see if it qualifies for this hotfix
Instance MSSQLSERVER does not meet the requirements for this HotFix or there
is no such instance installed on this computer
<EndFunc Name='QualifySQLInstance' Return='87' GetLastError='997'>
HotFix Installer did not find any installation or instance of SQL that quali
fies for this hotfix
<EndFunc Name='QualifySQLComputer' Return='1168' GetLastError='997'>
No components of SQL found on this computer that qualifies for this package.
<EndFunc Name='SQLHotfix' Return='1168' GetLastError='997'><EndFunc Name='Ha
ndlePackage' Return='1168' GetLastError='997'>
=== Completed processing package defined in Hotfix1.inf with return code: 11
68
=== Processing package defined in Hotfix2.inf
<Func Name='HandlePackage'>
=== PACKAGE INFORMATION
=== Starting Hotfix Build : 0818
=== Hotfix KB Article : 815495
=== Installer Base: Hotfix
=== TARGET PRODUCT FOR THIS HOTFIX (Requirements)
=== Target Product Name : SQL
=== Target Product Version : 8.00
=== Target Product Service Pack requirement : None
<Func Name='SQLHotfix'>
=== Hotfix targetting SQL Installations
<Func Name='PerformSQLDetection'><Func Name='CService::CService'><Func Name=
'CServiceNT::CServiceNT'><Func Name='CServiceNT::Open'><EndFunc Name='CServi
ceNT::Open' Return='T' GetLastError='997'><Func Name='CServiceNT::UpdateServ
iceStatus'><Func Name='CSer
viceNT::~CServiceNT'><Func Name='CServiceNT::Close'><EndFunc Name='CServiceN
T::Close' Return='T' GetLastError='997'><Func Name='CService::~CService'><Fu
nc Name='CService::CService'><Func Name='CServiceNT::CServiceNT'><Func Name=
'CServiceNT::Open'><EndFunc
Name='CServiceNT::Open' Return='T' GetLastError='997'><Func Name='CServiceNT
::UpdateServiceStatus'><Func Name='CServiceNT::~CServiceNT'><Func Name='CSer
viceNT::Close'><EndFunc Name='CServiceNT::Close' Return='T' GetLastError='99
7'><Func Name='CService::~
CService'><Func Name='GetProductCodeForInstance'><EndFunc Name='GetProductCo
deForInstance' Return='2' GetLastError='997'><EndFunc Name='PerformSQLDetect
ion' Return='0' GetLastError='997'><Func Name='CorrectCSDVersion'><EndFunc N
ame='CorrectCSDVersion' Ret
urn='0' GetLastError='0'><Func Name='PerformSQLDetection'><Func Name='CServi
ce::CService'><Func Name='CServiceNT::CServiceNT'><Func Name='CServiceNT::Op
en'><EndFunc Name='CServiceNT::Open' Return='T' GetLastError='997'><Func Nam
e='CServiceNT::UpdateServic
eStatus'><Func Name='CServiceNT::~CServiceNT'><Func Name='CServiceNT::Close'
><EndFunc Name='CServiceNT::Close' Return='T' GetLastError='997'><Func Name=
'CService::~CService'><Func Name='CService::CService'><Func Name='CServiceNT
::CServiceNT'><Func Name='C
ServiceNT::Open'><EndFunc Name='CServiceNT::Open' Return='T' GetLastError='9
97'><Func Name='CServiceNT::UpdateServiceStatus'><Func Name='CServiceNT::~CS
erviceNT'><Func Name='CServiceNT::Close'><EndFunc Name='CServiceNT::Close' R
eturn='T' GetLastError='997
'><Func Name='CService::~CService'><Func Name='GetProductCodeForInstance'><E
ndFunc Name='GetProductCodeForInstance' Return='2' GetLastError='997'><EndFu
nc Name='PerformSQLDetection' Return='0' GetLastError='997'><Func Name='Qual
ifySQLComputer'><Func Name=
'QualifySQLInstance'>
Verifying Instance MSSQLSERVER to see if it qualifies for this hotfix
Instance MSSQLSERVER does not meet the requirements for this HotFix or there
is no such instance installed on this computer
<EndFunc Name='QualifySQLInstance' Return='87' GetLastError='997'>
HotFix Installer did not find any installation or instance of SQL that quali
fies for this hotfix
<EndFunc Name='QualifySQLComputer' Return='1168' GetLastError='997'>
No components of SQL found on this computer that qualifies for this package.
<EndFunc Name='SQLHotfix' Return='1168' GetLastError='997'><EndFunc Name='Ha
ndlePackage' Return='1168' GetLastError='997'>
=== Completed processing package defined in Hotfix2.inf with return code: 11
68
=== Of the 2 packages no package qualified to run on this computer
<EndFunc Name='ProcessPackages' Return='1168' GetLastError='1813'><EndFunc N
ame='WinMain' Return='1168' GetLastError='1813'>|||Run the following command and post the results.
OSQL -E -Q"select @.@.version"
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Here is the output from the command. Thanks, John
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copy
right (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows N
T 5.0 (Build 2195: Service Pack 3)|||Review the following registry keys on your machine.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\CurrentVersion
\CSDVersion
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\CurrentVersion
\CSDVersionNumber
They should look like this:
CSDVersion (string) 8.00.761
CSDVersionNumber (dword) 300 (hex)
Update these keys as needed, and retry applying the Security Update.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)