MS SQL export / import data

Hi there,

I need to dump some data from a db by using MS Query. I noticed couple of issues during my attempts to do so. However I tried to run a query like:

SELECT table.column
INTO OUTFILE '/tmp/result.txt'
FROM table

which generated an error message:
Didn't expect "OUTFILE" after the SELECT column list.

Next I tried was:

SELECT table.column
FROM table
INTO OUTFILE '/tmp/result.txt'

generated another error:
Syntax error in FROM clause.

I also tried to define not only relative path to te result file but absolute path as well but it didn't help me a lot :-(
Could anybody help me what is theright syntx of this statement or is there some special way of MS Query to dump or export or write rows from the database into a file ?

Every suggestion will be higky appreciated

Tanks in advancewhy not try select col1name1, colname2, ... from tablename
then highlight the results, copy it and paste in a text editor eg notepad.
You can then save it and eventually open with excel.

MS SQL 2005, .NET, logins/sec and page faults

Hi, 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]

MS SQL 2000 SP Query Plan

I have a couple of complex stored procedures that work well and quickly
once they have compiled. The problem I am running into is that every
once in a while they want to refresh thier execution plans, and when
that happens it takes about 1 minute and 30 seconds for them to
rebuild, well of course my application is set up to time out commands
after 30 seconds so basicly the stored procedure never completes and
hangs up all of my subsequent stored procdures.

I have tried to use

OPTION KEEP FIXEDPLAN

on all of my select statments but I was wondering what else could be
done to stop a stored procedure from it's need to rebuild.

-AdamAdam --

I honestly don't think that what you think is happening is actually
happening. I think what might be more realistic is that one of your
stored procedures has started scanning a table, or acquiring a
long-lived lock, causing the others to slow down. Or perhaps something
else is acquiring a lock, slowing up your procedures. 1:30 to
recompile a query plan is an absolutely enormous amount of time. Keep
in mind that the time that it takes to run your query may vary by the
inputs that are passed to it. Have you run SQL Server Profiler and run
a trace? Look for large amounts of reads and writes associated with
the long duration of your stored procedures.

-Dave|||Adam Rogas (adam.rogas@.gmail.com) writes:
> I have a couple of complex stored procedures that work well and quickly
> once they have compiled. The problem I am running into is that every
> once in a while they want to refresh thier execution plans, and when
> that happens it takes about 1 minute and 30 seconds for them to
> rebuild, well of course my application is set up to time out commands
> after 30 seconds so basicly the stored procedure never completes and
> hangs up all of my subsequent stored procdures.
> I have tried to use
> OPTION KEEP FIXEDPLAN
> on all of my select statments but I was wondering what else could be
> done to stop a stored procedure from it's need to rebuild.

As Dave says, 1 minute for a recompilation is a very long time. There
is all reason to reinvestigate whether the diagnosis is correct. There
could be several other reasons for such stalls.

One way to test this is to run a copy of a procedure with a different
name from Query Analyzer, in this fashion:

CREATE PROCEDURE alternate_name AS ...
go
DECLARE @.d datetime
SELECT @.d = getdate()
EXEC alternate_name ...
PRINT 'First run took ' + ltrim(str(datediff(ms, @.d, getdate())
go
DECLARE @.d datetime
SELECT @.d = getdate()
EXEC alternate_name ...
PRINT 'Second run took ' + ltrim(str(datediff(ms, @.d, getdate())
go
EXEC sp_recompile alternate_name ...
go
DECLARE @.d datetime
SELECT @.d = getdate()
EXEC alternate_name ...
PRINT 'Third run took ' + ltrim(str(datediff(ms, @.d, getdate())

In the first run, there is no plan in csche, so the procedure will
be compiled at least once. Data may or may not be in cache. In the
second run, plan and data is in cache. In the third run, data is still
in cache, but the procedure will be compiled again. Thus, you should
compare the second and third runs.

The biggest procedure in our system is 3000 lines of code. It takes
about 8 seconds to compile. I've seen that queries with very long
IN lists (SELECT ... FROM tbl WHERE col IN (...)) with over 15000
elements can take up to 15 seconds to compile. That is still a far
cry from 90 seconds.

If you indeed have recompilation problems, you need to analyse what the
causes are. The SP:Recompile event populates the EventSubClass column,
values are documented here:
http://support.microsoft.com/defaul...b;EN-US;q308737.

The most likely reason is changed statistics. This white paper may give
guidance in such case:
http://www.microsoft.com/technet/pr...5/qrystats.mspx.

--
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

MS SQL 2000 Service Pack 4 schedule

Hi,
Could you please update me if the MS SQL 2000 SP 4 still scheduled? I found
some notifications about it couple month ago but the link takes me to another
product today.
We would like to be ready for new Service Pack and because of this i would
like to get estimated schedule of it.
Thanks
--
Eduard Timchenko
Business Technology Solutions Group
Verint SystemsHi
It is in beta. Everyone is expecting it in the next few weeks. No firm date
has been announced.
Regards
Mike
"Eduard Timchenko" wrote:
> Hi,
> Could you please update me if the MS SQL 2000 SP 4 still scheduled? I found
> some notifications about it couple month ago but the link takes me to another
> product today.
> We would like to be ready for new Service Pack and because of this i would
> like to get estimated schedule of it.
> Thanks
> --
> Eduard Timchenko
> Business Technology Solutions Group
> Verint Systems|||Hi Eduard,
The final release date of SQL2K SP4 has not been determined. But SQL Server
2000 Service Pack 4 Beta has been released. You can view the following page
to find more information about it:
http://support.microsoft.com/?id=290211
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: MS SQL 2000 Service Pack 4 schedule
>thread-index: AcU/MJpPyi/sRnNkRxWK332tUhpWGA==>X-WBNR-Posting-Host: 193.27.93.1
>From: "=?Utf-8?B?RWR1YXJkIFRpbWNoZW5rbw==?=" <etimche@.newsgroup.nospam>
>Subject: MS SQL 2000 Service Pack 4 schedule
>Date: Tue, 12 Apr 2005 00:24:02 -0700
>Lines: 13
>Message-ID: <5E14C38C-74E7-4BDF-B6F6-779C05F1C946@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:52094
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi,
>Could you please update me if the MS SQL 2000 SP 4 still scheduled? I
found
>some notifications about it couple month ago but the link takes me to
another
>product today.
>We would like to be ready for new Service Pack and because of this i would
>like to get estimated schedule of it.
>Thanks
>--
>Eduard Timchenko
>Business Technology Solutions Group
>Verint Systems
>

MS SQL 2000 Service Pack 4 schedule

Hi,
Could you please update me if the MS SQL 2000 SP 4 still scheduled? I found
some notifications about it couple month ago but the link takes me to anothe
r
product today.
We would like to be ready for new Service Pack and because of this i would
like to get estimated schedule of it.
Thanks
--
Eduard Timchenko
Business Technology Solutions Group
Verint SystemsHi
It is in beta. Everyone is expecting it in the next few weeks. No firm date
has been announced.
Regards
Mike
"Eduard Timchenko" wrote:

> Hi,
> Could you please update me if the MS SQL 2000 SP 4 still scheduled? I foun
d
> some notifications about it couple month ago but the link takes me to anot
her
> product today.
> We would like to be ready for new Service Pack and because of this i would
> like to get estimated schedule of it.
> Thanks
> --
> Eduard Timchenko
> Business Technology Solutions Group
> Verint Systems|||Hi Eduard,
The final release date of SQL2K SP4 has not been determined. But SQL Server
2000 Service Pack 4 Beta has been released. You can view the following page
to find more information about it:
http://support.microsoft.com/?id=290211
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: MS SQL 2000 Service Pack 4 schedule
>thread-index: AcU/MJpPyi/sRnNkRxWK332tUhpWGA==
>X-WBNR-Posting-Host: 193.27.93.1
>From: "examnotes" <etimche@.newsgroup.nospam>
>Subject: MS SQL 2000 Service Pack 4 schedule
>Date: Tue, 12 Apr 2005 00:24:02 -0700
>Lines: 13
>Message-ID: <5E14C38C-74E7-4BDF-B6F6-779C05F1C946@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:52094
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi,
>Could you please update me if the MS SQL 2000 SP 4 still scheduled? I
found
>some notifications about it couple month ago but the link takes me to
another
>product today.
>We would like to be ready for new Service Pack and because of this i would
>like to get estimated schedule of it.
>Thanks
>--
>Eduard Timchenko
>Business Technology Solutions Group
>Verint Systems
>

MS SQL 2000 Service Pack 4 schedule

Hi,
Could you please update me if the MS SQL 2000 SP 4 still scheduled? I found
some notifications about it couple month ago but the link takes me to another
product today.
We would like to be ready for new Service Pack and because of this i would
like to get estimated schedule of it.
Thanks
Eduard Timchenko
Business Technology Solutions Group
Verint Systems
Hi
It is in beta. Everyone is expecting it in the next few weeks. No firm date
has been announced.
Regards
Mike
"Eduard Timchenko" wrote:

> Hi,
> Could you please update me if the MS SQL 2000 SP 4 still scheduled? I found
> some notifications about it couple month ago but the link takes me to another
> product today.
> We would like to be ready for new Service Pack and because of this i would
> like to get estimated schedule of it.
> Thanks
> --
> Eduard Timchenko
> Business Technology Solutions Group
> Verint Systems
|||Hi Eduard,
The final release date of SQL2K SP4 has not been determined. But SQL Server
2000 Service Pack 4 Beta has been released. You can view the following page
to find more information about it:
http://support.microsoft.com/?id=290211
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>Thread-Topic: MS SQL 2000 Service Pack 4 schedule
>thread-index: AcU/MJpPyi/sRnNkRxWK332tUhpWGA==
>X-WBNR-Posting-Host: 193.27.93.1
>From: "=?Utf-8?B?RWR1YXJkIFRpbWNoZW5rbw==?=" <etimche@.newsgroup.nospam>
>Subject: MS SQL 2000 Service Pack 4 schedule
>Date: Tue, 12 Apr 2005 00:24:02 -0700
>Lines: 13
>Message-ID: <5E14C38C-74E7-4BDF-B6F6-779C05F1C946@.microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
>charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:52094
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi,
>Could you please update me if the MS SQL 2000 SP 4 still scheduled? I
found
>some notifications about it couple month ago but the link takes me to
another
>product today.
>We would like to be ready for new Service Pack and because of this i would
>like to get estimated schedule of it.
>Thanks
>--
>Eduard Timchenko
>Business Technology Solutions Group
>Verint Systems
>

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...

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:

---

> this error. Thanks, John

---

|||Thanks, found the log files.
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.