Post-sp3a Patches?

Are there any patches are updates for SQL Server 2000 that are NOT included
in service pack 3a? I have a customer thinking that additional sql server
patches are required on a server but I don't believe that there are any that
are not already included in 3a which this server has.
Thanks.
MichelleI found this from July 2003:
http://www.microsoft.com/technet/se...n/MS03-031.mspx
I think that's everything.
"michelle" <michelle@.nospam.com> wrote in message
news:OL$aOsN9EHA.4004@.tk2msftngp13.phx.gbl...
> Are there any patches are updates for SQL Server 2000 that are NOT
included
> in service pack 3a? I have a customer thinking that additional sql server
> patches are required on a server but I don't believe that there are any
that
> are not already included in 3a which this server has.
> Thanks.
> Michelle
>|||Michelle,
SP4 is just going into beta. See
http://support.microsoft.com/defaul...kb;en-us;888799 for fixes
included.
Chris Wood
"michelle" <michelle@.nospam.com> wrote in message
news:%23bXn8UO9EHA.1292@.TK2MSFTNGP10.phx.gbl...
> I found this from July 2003:
> http://www.microsoft.com/technet/se...n/MS03-031.mspx
> I think that's everything.
> "michelle" <michelle@.nospam.com> wrote in message
> news:OL$aOsN9EHA.4004@.tk2msftngp13.phx.gbl...
> included
server[vbcol=seagreen]
> that
>sql

POSTED AGAIN- DISTRIBUTED TRANSACTION

Hi,
I have two sql servers with SQL2000 service pack 3 which are linked by the
"Link Server". When i use the "begin tran" (distributed transaction) in
stored procedure, i am getting the following error.
"Server: Msg 8525, Level 16, State 1, Line 1
Distributed transaction completed. Either enlist this session in a new
transaction or the NULL transaction. "
The following article talks about this problem.
http://support.microsoft.com/?kbid=834849
But, both servers are SQL 2000 in my case. Any help?
Thanks,
VijayVijay,
Try rerun the same Instcat.sql described in the kb again on each node. This
will ensure that they have the correct catalog sprocs.
-oj
"Vijay" <vijay@.infosysusa.com> wrote in message
news:%23yRbv$LBFHA.1200@.tk2msftngp13.phx.gbl...
> Hi,
>
> I have two sql servers with SQL2000 service pack 3 which are linked by the
> "Link Server". When i use the "begin tran" (distributed transaction) in
> stored procedure, i am getting the following error.
>
> "Server: Msg 8525, Level 16, State 1, Line 1
> Distributed transaction completed. Either enlist this session in a new
> transaction or the NULL transaction. "
>
> The following article talks about this problem.
> http://support.microsoft.com/?kbid=834849
> But, both servers are SQL 2000 in my case. Any help?
>
> Thanks,
> Vijay
>
>|||I don't think so. It is working for other distributed queries. Any other
solutions please?
Thanks,
Vijay
"oj" <nospam_ojngo@.home.com> wrote in message
news:%23bSADGMBFHA.1076@.TK2MSFTNGP10.phx.gbl...
> Vijay,
> Try rerun the same Instcat.sql described in the kb again on each node.
This
> will ensure that they have the correct catalog sprocs.
> --
> -oj
>
> "Vijay" <vijay@.infosysusa.com> wrote in message
> news:%23yRbv$LBFHA.1200@.tk2msftngp13.phx.gbl...
the
>|||Vijay,
What do you mean "It is working for other distributed queries". If you only
encounter the error on enlisting a distributed transaction, I suggest you
take a look at your linkedserver logins. Also, check to make sure DTC
services are using proper accounts. If they're started under LocalSystem, it
will not have access to network resources. If you are going to make any
changes to your DTC services, you will have to restart SQL server for it to
takes effect.
-oj
"Vijay" <vijay@.infosysusa.com> wrote in message
news:eKKqhVMBFHA.1992@.TK2MSFTNGP10.phx.gbl...
>I don't think so. It is working for other distributed queries. Any other
> solutions please?
> Thanks,
> Vijay
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:%23bSADGMBFHA.1076@.TK2MSFTNGP10.phx.gbl...
> This
> the
>

Post update for SQLServer SP2--is there one for SQLServer Express?

Regarding KB935356, is there a "post" service pack 2 update for SQLServer Express?

Thanks.

hi,

LizWard wrote:

Regarding KB935356, is there a "post" service pack 2 update for SQLServer Express?

Thanks.

I'm currently at 3159 build (both on SQL Server 2005 Dev editions and SQLEpxress), so I did not install 3161, but the "Applies to" section reports SQLExpress and SQLExpress With Advanced Services as well, so you should be able to install it on them, as long as you really need them and contact Microsoft for it..

regards

|||For SQLExpress, you stated that you are currently on build 3159. Where did you get that build from? I'm currently on this version:

9.00.3042.00.

I downloaded what seemed to be the latest SQLExpress...please send the URL that you used.

Thanks very much.

|||

hi,

it's "linked" above in the "3159" word

anyway, it's at http://support.microsoft.com/default.aspx/kb/934459/en-us

regards

|||

Andrea:

There is a later one: http://support.microsoft.com/kb/935356/en-us which is Build 3161 -- Article dated 4/19/2007.

Our company has that one downloaded so I will try it when I go "off call" next Wednesday.

Thanks for your help....I hope it will work on SQLExpress.

Lisa

|||

Andrea:

I was able to apply the hotfix that I mentioned in my post on 4/19. Sorry for the delay in replying.

Thanks for your help.

Lisa

sql

Post update for SQLServer SP2--is there one for SQLServer Express?

Regarding KB935356, is there a "post" service pack 2 update for SQLServer Express?

Thanks.

hi,

LizWard wrote:

Regarding KB935356, is there a "post" service pack 2 update for SQLServer Express?

Thanks.

I'm currently at 3159 build (both on SQL Server 2005 Dev editions and SQLEpxress), so I did not install 3161, but the "Applies to" section reports SQLExpress and SQLExpress With Advanced Services as well, so you should be able to install it on them, as long as you really need them and contact Microsoft for it..

regards

|||For SQLExpress, you stated that you are currently on build 3159. Where did you get that build from? I'm currently on this version:

9.00.3042.00.

I downloaded what seemed to be the latest SQLExpress...please send the URL that you used.

Thanks very much.

|||

hi,

it's "linked" above in the "3159" word

anyway, it's at http://support.microsoft.com/default.aspx/kb/934459/en-us

regards

|||

Andrea:

There is a later one: http://support.microsoft.com/kb/935356/en-us which is Build 3161 -- Article dated 4/19/2007.

Our company has that one downloaded so I will try it when I go "off call" next Wednesday.

Thanks for your help....I hope it will work on SQLExpress.

Lisa

|||

Andrea:

I was able to apply the hotfix that I mentioned in my post on 4/19. Sorry for the delay in replying.

Thanks for your help.

Lisa

Post SP3 Full text performance degradation

Since upgrading to service pack 3a (from sql server with
no sp) I am experiencing performance issues with my full
text searches. Its hard to quantify the problem - but
since the upgrade I am definitely seeing significatnt
increase in duration for searches - especially when they
run concurrently.
As part of the upgrade the catalogs were rebuilt.
Any ideas would be appreciated
This is abnormal. There were some problems with the search algorithim prior
to SP 3 relating to ranking. If you are doing ordering you may experieince
some difference in performance.
I noticed a performance increase. How many simultaneous queries are you
running? You can get this metric by looking at the performance monitor
counter Microsoft Search:Queries
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"rob" <anonymous@.discussions.microsoft.com> wrote in message
news:3ff201c4ab8e$5a1c3400$a301280a@.phx.gbl...
> Since upgrading to service pack 3a (from sql server with
> no sp) I am experiencing performance issues with my full
> text searches. Its hard to quantify the problem - but
> since the upgrade I am definitely seeing significatnt
> increase in duration for searches - especially when they
> run concurrently.
> As part of the upgrade the catalogs were rebuilt.
> Any ideas would be appreciated
|||Hilary,
Right now it is running at an average of about 300000, but
we are experiencing light load, and we are having no
problem. I'll keep the metric running and monitor what
happens when we do have problems.
The stored procedure that runs the various
containscontable commands uses dynamic sql, and also joins
on tables in other databases on the same server - do you
know if either of these aspects could have been affected
by SP3. I have made no code changes that would account
for the problems I am seeing.
THanks, Rob
>--Original Message--
>This is abnormal. There were some problems with the
search algorithim prior
>to SP 3 relating to ranking. If you are doing ordering
you may experieince
>some difference in performance.
>I noticed a performance increase. How many simultaneous
queries are you
>running? You can get this metric by looking at the
performance monitor
>counter Microsoft Search:Queries
>--
>Hilary Cotter
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>"rob" <anonymous@.discussions.microsoft.com> wrote in
message
>news:3ff201c4ab8e$5a1c3400$a301280a@.phx.gbl...
>
>.
>
|||Hilary,
I just saw the cpu flat-lining again, but the metric did
not really change.
Rob
>--Original Message--
>This is abnormal. There were some problems with the
search algorithim prior
>to SP 3 relating to ranking. If you are doing ordering
you may experieince
>some difference in performance.
>I noticed a performance increase. How many simultaneous
queries are you
>running? You can get this metric by looking at the
performance monitor
>counter Microsoft Search:Queries
>--
>Hilary Cotter
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
>"rob" <anonymous@.discussions.microsoft.com> wrote in
message
>news:3ff201c4ab8e$5a1c3400$a301280a@.phx.gbl...
>
>.
>
|||are there any error messages in the event log from MSSearch or MSSCi?
When you say you saw the CPU flat lining I take it, that CPU is going to
100%, or it is remaining constant?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
<anonymous@.discussions.microsoft.com> wrote in message
news:333301c4aba7$988ef3d0$a501280a@.phx.gbl...[vbcol=seagreen]
> Hilary,
> I just saw the cpu flat-lining again, but the metric did
> not really change.
> Rob
> search algorithim prior
> you may experieince
> queries are you
> performance monitor
> message
|||There are no errors or warnings - and the searches do
return after several seconds, but they run the cpu at 100%
until they return, and are much slower than before SP3 was
installed.
Do you think the problem could be related to cross-
database queries or dynamic sql?
Rob
>--Original Message--
>are there any error messages in the event log from
MSSearch or MSSCi?
>When you say you saw the CPU flat lining I take it, that
CPU is going to[vbcol=seagreen]
>100%, or it is remaining constant?
>--
>Hilary Cotter
>Looking for a SQL Server replication book?
>http://www.nwsu.com/0974973602.html
>
><anonymous@.discussions.microsoft.com> wrote in message
>news:333301c4aba7$988ef3d0$a501280a@.phx.gbl...
with[vbcol=seagreen]
full[vbcol=seagreen]
but[vbcol=seagreen]
they
>
>.
>
|||dynamic sql is often inefficient, but not always as in some cases the
execution plan will be cached and reused.
However, in the type of queries you would use with SQL FTS it is not cached.
It could be related to cross database queries, especially if you are not
fully qualifying your database and owner names.
Can you post your query here? Also how many queries are occuring per second
or minute? And how many rows are in your table?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
<anonymous@.discussions.microsoft.com> wrote in message
news:36bb01c4abca$99400670$a501280a@.phx.gbl...[vbcol=seagreen]
> There are no errors or warnings - and the searches do
> return after several seconds, but they run the cpu at 100%
> until they return, and are much slower than before SP3 was
> installed.
> Do you think the problem could be related to cross-
> database queries or dynamic sql?
> Rob
> MSSearch or MSSCi?
> CPU is going to
> with
> full
> but
> they
|||Rob,
There were several MAJOR fixes related to FTS in SQL Server 2000 SP3 that
caused existing FT Catalogs to be automatically rebuilt (if you selected
them during the SP3 installation) or your could of deferred the rebuild if
the FT Catalogs were large and use the procedures in KB article Q240867 at a
later point in time. Do you know which option you selected during the SP3
upgrade?
Below are two KB articles that document these fixes related to FTS in SP3:
327217 (Q327217) INF: Installing SQL Server 2000 Service Pack 3 Rebuilds All
Full-Text Catalogs
http://support.microsoft.com/default...b;en-us;327217
312410 (Q312410) "FIX: Full Text RANK Results May Vary After Catalog
Repopulation"
http://support.microsoft.com/default...b;en-us;312410 (references
Q240867)
Regards,
John
<anonymous@.discussions.microsoft.com> wrote in message
news:36bb01c4abca$99400670$a501280a@.phx.gbl...[vbcol=seagreen]
> There are no errors or warnings - and the searches do
> return after several seconds, but they run the cpu at 100%
> until they return, and are much slower than before SP3 was
> installed.
> Do you think the problem could be related to cross-
> database queries or dynamic sql?
> Rob
> MSSearch or MSSCi?
> CPU is going to
> with
> full
> but
> they

possible bug regarding single line comments in SQL Server Management Studio

I don't know if this is a bug or something I've messed up in my settings. I am using SQL Server Management Studio with SQL 2005 service pack 1 installed, and I've been using it successfully ever since SP1 came out. All of a sudden, any time I have a query with a single line comment (i.e. using dash dash -- ), the rest of the query is ignored as if the single line comment is really a multi-line comment without the closing */

An example:

select top 100 *

from myTable

-- this is a comment

where myTableID = 1234

This would normally return exactly one row, but instead returns 100 rows ( as if the where clause did not exist). If I move the where clause above the comment, it works as expected. Any ideas?

In trying to fix this, I've uninstalled and reinstalled and even reinstalled SP1, but it still isn't fixed.

You've got me stumped. I took the code you have posted and it ran fine for me.

Can you post the exact code that you are using? Maybe we'll see that hanging character you missed or somthing.

|||

I used the exact query, merely changing the table name and ID column.

I ended up going through the process yet again (uninstalling the tools, reinstalling the tools, then installing SP1) and rebooted but still had the problem. However, after a second reboot, it starting behaving properly again. I hope my problem does not resurface.

|||We (me a colleague of mine), have withnessed this same behaviour and, atfer some deep analysis, we have concluded that this bug arises when the Transact-Sql line terminates with a CR (Carriage Return, Ascii(13)) only charaters when it should terminate with both CR (Carriage Return, Ascii(13)) followed by an LF (Line Feed, Ascii(10))

It seems that once SqlServer reachs a single-line comment identifier (--) it keeps fetching bytes untill a compounded line termination (CR followed by LF) is reached.

In the following sample, the {CR+LF} and {CR} are representations of their respective invisible ascii codes.

--This is just a normal single-line comment {CR+LF}
SELECT 'This command works fine' {CR+LF}

--This is a buggy single-line comment {CR}
SELECT 'This command does not work'{CR}
SELECT 'This command does not work either' {CR+LF}
SELECT 'This command work fine too' {CR+LF}

Moreover we have reasons to bellieve that this bug resides in Query Editor provided with SQL Server Management Studio Express Edition (at least, this was version my colleague was using when this bug arose). Anyway, although this bug must be corrected, LF should just be ignored when dealing with Sql scripts.

Running software:

SQL Server Management Studio Express Edition

Ms SQLServer 2000 (8.0.2039)

Win XP Portuguese SP2

Getting this sample you can:

- Load and execute it, using QueryAnalyzer to see the refered behaviour;
- View it, using Notepad, to see what actually happened.

possible bug regarding single line comments in SQL Server Management Studio

I don't know if this is a bug or something I've messed up in my settings. I am using SQL Server Management Studio with SQL 2005 service pack 1 installed, and I've been using it successfully ever since SP1 came out. All of a sudden, any time I have a query with a single line comment (i.e. using dash dash -- ), the rest of the query is ignored as if the single line comment is really a multi-line comment without the closing */

An example:

select top 100 *

from myTable

-- this is a comment

where myTableID = 1234

This would normally return exactly one row, but instead returns 100 rows ( as if the where clause did not exist). If I move the where clause above the comment, it works as expected. Any ideas?

In trying to fix this, I've uninstalled and reinstalled and even reinstalled SP1, but it still isn't fixed.

You've got me stumped. I took the code you have posted and it ran fine for me.

Can you post the exact code that you are using? Maybe we'll see that hanging character you missed or somthing.

|||

I used the exact query, merely changing the table name and ID column.

I ended up going through the process yet again (uninstalling the tools, reinstalling the tools, then installing SP1) and rebooted but still had the problem. However, after a second reboot, it starting behaving properly again. I hope my problem does not resurface.

|||We (me a colleague of mine), have withnessed this same behaviour and, atfer some deep analysis, we have concluded that this bug arises when the Transact-Sql line terminates with a CR (Carriage Return, Ascii(13)) only charaters when it should terminate with both CR (Carriage Return, Ascii(13)) followed by an LF (Line Feed, Ascii(10))

It seems that once SqlServer reachs a single-line comment identifier (--) it keeps fetching bytes untill a compounded line termination (CR followed by LF) is reached.

In the following sample, the {CR+LF} and {CR} are representations of their respective invisible ascii codes.

--This is just a normal single-line comment {CR+LF}
SELECT 'This command works fine' {CR+LF}

--This is a buggy single-line comment {CR}
SELECT 'This command does not work'{CR}
SELECT 'This command does not work either' {CR+LF}
SELECT 'This command work fine too' {CR+LF}

Moreover we have reasons to bellieve that this bug resides in Query Editor provided with SQL Server Management Studio Express Edition (at least, this was version my colleague was using when this bug arose). Anyway, although this bug must be corrected, LF should just be ignored when dealing with Sql scripts.

Running software:

SQL Server Management Studio Express Edition

Ms SQLServer 2000 (8.0.2039)

Win XP Portuguese SP2

Getting this sample you can:

- Load and execute it, using QueryAnalyzer to see the refered behaviour;
- View it, using Notepad, to see what actually happened.