I ran this script to backup to restore a backup onto a database with a new
name - on the same server.
USE master
> RESTORE DATABASE DBnew
> FROM DISK = 'E:\MSSQL7\BACKUP\DBold_db_200409270201.BAK'
> with RECOVERY,
> MOVE 'DBold_Data' TO 'E:\MSSQL7\data\DBnew_Data.MDF',
> MOVE 'DBold_Log' TO 'E:\MSSQL7\data\DBnew_Log.LDF',
> REPLACE
When I look at the properties for the database under em, I see that both the
original database and the copy-of-it-with-a-new-name have the same "File
Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
"Transaction Files" tabs. The "Location", which points to the actual
physical file, is correctly and uniquely named.
Is the fact that these have the same File Name going to confuse SQL Server
when it goes to update a database?You should be fine.
"MarkAurit" <MarkAurit@.discussions.microsoft.com> wrote in message
news:59CC2C26-13F8-4664-99F1-CC550827A9D4@.microsoft.com...
>I ran this script to backup to restore a backup onto a database with a new
> name - on the same server.
> USE master
> When I look at the properties for the database under em, I see that both
> the
> original database and the copy-of-it-with-a-new-name have the same "File
> Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
> "Transaction Files" tabs. The "Location", which points to the actual
> physical file, is correctly and uniquely named.
> Is the fact that these have the same File Name going to confuse SQL Server
> when it goes to update a database?
Showing posts with label ran. Show all posts
Showing posts with label ran. Show all posts
Friday, March 9, 2012
Issue with restore to new dbname on same server
I ran this script to backup to restore a backup onto a database with a new
name - on the same server.
USE master
> RESTORE DATABASE DBnew
> FROM DISK = 'E:\MSSQL7\BACKUP\DBold_db_200409270201.BAK'
> with RECOVERY,
> MOVE 'DBold_Data' TO 'E:\MSSQL7\data\DBnew_Data.MDF',
> MOVE 'DBold_Log' TO 'E:\MSSQL7\data\DBnew_Log.LDF',
> REPLACE
When I look at the properties for the database under em, I see that both the
original database and the copy-of-it-with-a-new-name have the same "File
Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
"Transaction Files" tabs. The "Location", which points to the actual
physical file, is correctly and uniquely named.
Is the fact that these have the same File Name going to confuse SQL Server
when it goes to update a database?
You should be fine.
"MarkAurit" <MarkAurit@.discussions.microsoft.com> wrote in message
news:59CC2C26-13F8-4664-99F1-CC550827A9D4@.microsoft.com...
>I ran this script to backup to restore a backup onto a database with a new
> name - on the same server.
> USE master
> When I look at the properties for the database under em, I see that both
> the
> original database and the copy-of-it-with-a-new-name have the same "File
> Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
> "Transaction Files" tabs. The "Location", which points to the actual
> physical file, is correctly and uniquely named.
> Is the fact that these have the same File Name going to confuse SQL Server
> when it goes to update a database?
name - on the same server.
USE master
> RESTORE DATABASE DBnew
> FROM DISK = 'E:\MSSQL7\BACKUP\DBold_db_200409270201.BAK'
> with RECOVERY,
> MOVE 'DBold_Data' TO 'E:\MSSQL7\data\DBnew_Data.MDF',
> MOVE 'DBold_Log' TO 'E:\MSSQL7\data\DBnew_Log.LDF',
> REPLACE
When I look at the properties for the database under em, I see that both the
original database and the copy-of-it-with-a-new-name have the same "File
Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
"Transaction Files" tabs. The "Location", which points to the actual
physical file, is correctly and uniquely named.
Is the fact that these have the same File Name going to confuse SQL Server
when it goes to update a database?
You should be fine.
"MarkAurit" <MarkAurit@.discussions.microsoft.com> wrote in message
news:59CC2C26-13F8-4664-99F1-CC550827A9D4@.microsoft.com...
>I ran this script to backup to restore a backup onto a database with a new
> name - on the same server.
> USE master
> When I look at the properties for the database under em, I see that both
> the
> original database and the copy-of-it-with-a-new-name have the same "File
> Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
> "Transaction Files" tabs. The "Location", which points to the actual
> physical file, is correctly and uniquely named.
> Is the fact that these have the same File Name going to confuse SQL Server
> when it goes to update a database?
Issue with restore to new dbname on same server
I ran this script to backup to restore a backup onto a database with a new
name - on the same server.
USE master
> RESTORE DATABASE DBnew
> FROM DISK = 'E:\MSSQL7\BACKUP\DBold_db_200409270201.BAK'
> with RECOVERY,
> MOVE 'DBold_Data' TO 'E:\MSSQL7\data\DBnew_Data.MDF',
> MOVE 'DBold_Log' TO 'E:\MSSQL7\data\DBnew_Log.LDF',
> REPLACE
When I look at the properties for the database under em, I see that both the
original database and the copy-of-it-with-a-new-name have the same "File
Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
"Transaction Files" tabs. The "Location", which points to the actual
physical file, is correctly and uniquely named.
Is the fact that these have the same File Name going to confuse SQL Server
when it goes to update a database?You should be fine.
"MarkAurit" <MarkAurit@.discussions.microsoft.com> wrote in message
news:59CC2C26-13F8-4664-99F1-CC550827A9D4@.microsoft.com...
>I ran this script to backup to restore a backup onto a database with a new
> name - on the same server.
> USE master
>> RESTORE DATABASE DBnew
>> FROM DISK = 'E:\MSSQL7\BACKUP\DBold_db_200409270201.BAK'
>> with RECOVERY,
>> MOVE 'DBold_Data' TO 'E:\MSSQL7\data\DBnew_Data.MDF',
>> MOVE 'DBold_Log' TO 'E:\MSSQL7\data\DBnew_Log.LDF',
>> REPLACE
> When I look at the properties for the database under em, I see that both
> the
> original database and the copy-of-it-with-a-new-name have the same "File
> Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
> "Transaction Files" tabs. The "Location", which points to the actual
> physical file, is correctly and uniquely named.
> Is the fact that these have the same File Name going to confuse SQL Server
> when it goes to update a database?
name - on the same server.
USE master
> RESTORE DATABASE DBnew
> FROM DISK = 'E:\MSSQL7\BACKUP\DBold_db_200409270201.BAK'
> with RECOVERY,
> MOVE 'DBold_Data' TO 'E:\MSSQL7\data\DBnew_Data.MDF',
> MOVE 'DBold_Log' TO 'E:\MSSQL7\data\DBnew_Log.LDF',
> REPLACE
When I look at the properties for the database under em, I see that both the
original database and the copy-of-it-with-a-new-name have the same "File
Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
"Transaction Files" tabs. The "Location", which points to the actual
physical file, is correctly and uniquely named.
Is the fact that these have the same File Name going to confuse SQL Server
when it goes to update a database?You should be fine.
"MarkAurit" <MarkAurit@.discussions.microsoft.com> wrote in message
news:59CC2C26-13F8-4664-99F1-CC550827A9D4@.microsoft.com...
>I ran this script to backup to restore a backup onto a database with a new
> name - on the same server.
> USE master
>> RESTORE DATABASE DBnew
>> FROM DISK = 'E:\MSSQL7\BACKUP\DBold_db_200409270201.BAK'
>> with RECOVERY,
>> MOVE 'DBold_Data' TO 'E:\MSSQL7\data\DBnew_Data.MDF',
>> MOVE 'DBold_Log' TO 'E:\MSSQL7\data\DBnew_Log.LDF',
>> REPLACE
> When I look at the properties for the database under em, I see that both
> the
> original database and the copy-of-it-with-a-new-name have the same "File
> Name" (DBold_Data and DBold_Log, respectively) under the "Data Files" and
> "Transaction Files" tabs. The "Location", which points to the actual
> physical file, is correctly and uniquely named.
> Is the fact that these have the same File Name going to confuse SQL Server
> when it goes to update a database?
Issue with Installation of Service Pack 3a
All,
I successfully ran SQL Server Service Pack 3a on a machine that has two
instances of SQL Server. I ran the service pack against both instances. It
all appeared to run fine and I rebooted.
However, when I run the following select statement in Query Analyser:
select @.@.version
It is showing me:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
that the instances are at service pack 3a.
Did my service pack really run successfully? Is this a known issue?
Thanks,
Andrea Wright
andrea.wright@.ips-sendero.com
Hi Andrea,
The version of sql server you are running is 8.00.818 which is a hotfixed
version of SQL server later than than sp3 (which is version 8.00.760).
Actually the 818 version is coming with the public critical SQL server
security roll up fix MS03-031. I Expect you have installed this SQL server
security fix after you've installed sp3.
Regards,
Jago
"Andrea Wright" wrote:
> All,
> I successfully ran SQL Server Service Pack 3a on a machine that has two
> instances of SQL Server. I ran the service pack against both instances. It
> all appeared to run fine and I rebooted.
> However, when I run the following select statement in Query Analyser:
> select @.@.version
> It is showing me:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> that the instances are at service pack 3a.
> Did my service pack really run successfully? Is this a known issue?
> Thanks,
> Andrea Wright
> andrea.wright@.ips-sendero.com
>
>
|||Jago,
Thanks for your quick response.
I installed the following in this order:
Hotfix that fixed the security issue and the Slammer virus (Microsoft SQL
Server 2000 - 8.00.679)
Service Pack 3 (not sure of the number this put it at)
Service Pack 3a (Microsoft SQL Server 2000 - 8.00.760)
I did not realize there was another hotfix, and I didn't apply one manually.
Is this one perhaps coming with Windows updates?
Thanks,
Andrea
"Jago" <Jago@.discussions.microsoft.com> wrote in message
news:B676216C-B1D0-4F05-A8A8-213BD997DC76@.microsoft.com...[vbcol=seagreen]
> Hi Andrea,
> The version of sql server you are running is 8.00.818 which is a hotfixed
> version of SQL server later than than sp3 (which is version 8.00.760).
> Actually the 818 version is coming with the public critical SQL server
> security roll up fix MS03-031. I Expect you have installed this SQL server
> security fix after you've installed sp3.
> Regards,
> Jago
> "Andrea Wright" wrote:
|||Hi Andre,
No was not coming with windows update
Jago
"Andrea Wright" wrote:
> Jago,
> Thanks for your quick response.
> I installed the following in this order:
> Hotfix that fixed the security issue and the Slammer virus (Microsoft SQL
> Server 2000 - 8.00.679)
> Service Pack 3 (not sure of the number this put it at)
> Service Pack 3a (Microsoft SQL Server 2000 - 8.00.760)
> I did not realize there was another hotfix, and I didn't apply one manually.
> Is this one perhaps coming with Windows updates?
> Thanks,
> Andrea
> "Jago" <Jago@.discussions.microsoft.com> wrote in message
> news:B676216C-B1D0-4F05-A8A8-213BD997DC76@.microsoft.com...
>
>
|||To confirm whether you are on SP3a, run the following command.
select serverproperty('productLevel')
Andrea Wright wrote:
> All,
> I successfully ran SQL Server Service Pack 3a on a machine that has two
> instances of SQL Server. I ran the service pack against both instances. It
> all appeared to run fine and I rebooted.
> However, when I run the following select statement in Query Analyser:
> select @.@.version
> It is showing me:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> that the instances are at service pack 3a.
> Did my service pack really run successfully? Is this a known issue?
> Thanks,
> Andrea Wright
> andrea.wright@.ips-sendero.com
>
|||"Jonathan Yong" <jyong@.someplace.net> wrote in message
news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
> To confirm whether you are on SP3a, run the following command.
> select serverproperty('productLevel')
And it should return... ? I "thought" I had SP3a - I definitely applied it
and received no errors. But I just ran this and it returns "SP3". When I
select @.@.version, I get 8.00.760.
[vbcol=seagreen]
>
> Andrea Wright wrote:
It[vbcol=seagreen]
indicate[vbcol=seagreen]
|||Mine says SP3 as well - the a is missing...
-- Andrea
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
news:ug0$JutsEHA.3320@.TK2MSFTNGP15.phx.gbl...
> "Jonathan Yong" <jyong@.someplace.net> wrote in message
> news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
> And it should return... ? I "thought" I had SP3a - I definitely applied it
> and received no errors. But I just ran this and it returns "SP3". When I
> select @.@.version, I get 8.00.760.
> It
> indicate
>
|||AFIK, SQL Server doesn't differentiate between SP 3 and SP 3a with Select
@.@.version or any other method in the database itself. You can look in the
registry for the correct version. If you're running SQL Server, run regedit
and locate HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\Cu rrentVersion.
Then look at the CSDVersion value. It should be 8.00.761 for SP 3a,
8.00.760 for SP 3. There's also a file or two you can check for version
info in Windows Explorer, but I don't remember which ones off the top of my
head.
Thanks,
Michael C., MCDBA
"Andrea Wright" <andrea.wright@.ips-sendero.com#nospam> wrote in message
news:%23XbgujRtEHA.1040@.TK2MSFTNGP10.phx.gbl...
> Mine says SP3 as well - the a is missing...
> -- Andrea
> "Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
> news:ug0$JutsEHA.3320@.TK2MSFTNGP15.phx.gbl...
>
I successfully ran SQL Server Service Pack 3a on a machine that has two
instances of SQL Server. I ran the service pack against both instances. It
all appeared to run fine and I rebooted.
However, when I run the following select statement in Query Analyser:
select @.@.version
It is showing me:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
that the instances are at service pack 3a.
Did my service pack really run successfully? Is this a known issue?
Thanks,
Andrea Wright
andrea.wright@.ips-sendero.com
Hi Andrea,
The version of sql server you are running is 8.00.818 which is a hotfixed
version of SQL server later than than sp3 (which is version 8.00.760).
Actually the 818 version is coming with the public critical SQL server
security roll up fix MS03-031. I Expect you have installed this SQL server
security fix after you've installed sp3.
Regards,
Jago
"Andrea Wright" wrote:
> All,
> I successfully ran SQL Server Service Pack 3a on a machine that has two
> instances of SQL Server. I ran the service pack against both instances. It
> all appeared to run fine and I rebooted.
> However, when I run the following select statement in Query Analyser:
> select @.@.version
> It is showing me:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> that the instances are at service pack 3a.
> Did my service pack really run successfully? Is this a known issue?
> Thanks,
> Andrea Wright
> andrea.wright@.ips-sendero.com
>
>
|||Jago,
Thanks for your quick response.
I installed the following in this order:
Hotfix that fixed the security issue and the Slammer virus (Microsoft SQL
Server 2000 - 8.00.679)
Service Pack 3 (not sure of the number this put it at)
Service Pack 3a (Microsoft SQL Server 2000 - 8.00.760)
I did not realize there was another hotfix, and I didn't apply one manually.
Is this one perhaps coming with Windows updates?
Thanks,
Andrea
"Jago" <Jago@.discussions.microsoft.com> wrote in message
news:B676216C-B1D0-4F05-A8A8-213BD997DC76@.microsoft.com...[vbcol=seagreen]
> Hi Andrea,
> The version of sql server you are running is 8.00.818 which is a hotfixed
> version of SQL server later than than sp3 (which is version 8.00.760).
> Actually the 818 version is coming with the public critical SQL server
> security roll up fix MS03-031. I Expect you have installed this SQL server
> security fix after you've installed sp3.
> Regards,
> Jago
> "Andrea Wright" wrote:
|||Hi Andre,
No was not coming with windows update
Jago
"Andrea Wright" wrote:
> Jago,
> Thanks for your quick response.
> I installed the following in this order:
> Hotfix that fixed the security issue and the Slammer virus (Microsoft SQL
> Server 2000 - 8.00.679)
> Service Pack 3 (not sure of the number this put it at)
> Service Pack 3a (Microsoft SQL Server 2000 - 8.00.760)
> I did not realize there was another hotfix, and I didn't apply one manually.
> Is this one perhaps coming with Windows updates?
> Thanks,
> Andrea
> "Jago" <Jago@.discussions.microsoft.com> wrote in message
> news:B676216C-B1D0-4F05-A8A8-213BD997DC76@.microsoft.com...
>
>
|||To confirm whether you are on SP3a, run the following command.
select serverproperty('productLevel')
Andrea Wright wrote:
> All,
> I successfully ran SQL Server Service Pack 3a on a machine that has two
> instances of SQL Server. I ran the service pack against both instances. It
> all appeared to run fine and I rebooted.
> However, when I run the following select statement in Query Analyser:
> select @.@.version
> It is showing me:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> that the instances are at service pack 3a.
> Did my service pack really run successfully? Is this a known issue?
> Thanks,
> Andrea Wright
> andrea.wright@.ips-sendero.com
>
|||"Jonathan Yong" <jyong@.someplace.net> wrote in message
news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
> To confirm whether you are on SP3a, run the following command.
> select serverproperty('productLevel')
And it should return... ? I "thought" I had SP3a - I definitely applied it
and received no errors. But I just ran this and it returns "SP3". When I
select @.@.version, I get 8.00.760.
[vbcol=seagreen]
>
> Andrea Wright wrote:
It[vbcol=seagreen]
indicate[vbcol=seagreen]
|||Mine says SP3 as well - the a is missing...
-- Andrea
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
news:ug0$JutsEHA.3320@.TK2MSFTNGP15.phx.gbl...
> "Jonathan Yong" <jyong@.someplace.net> wrote in message
> news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
> And it should return... ? I "thought" I had SP3a - I definitely applied it
> and received no errors. But I just ran this and it returns "SP3". When I
> select @.@.version, I get 8.00.760.
> It
> indicate
>
|||AFIK, SQL Server doesn't differentiate between SP 3 and SP 3a with Select
@.@.version or any other method in the database itself. You can look in the
registry for the correct version. If you're running SQL Server, run regedit
and locate HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\Cu rrentVersion.
Then look at the CSDVersion value. It should be 8.00.761 for SP 3a,
8.00.760 for SP 3. There's also a file or two you can check for version
info in Windows Explorer, but I don't remember which ones off the top of my
head.
Thanks,
Michael C., MCDBA
"Andrea Wright" <andrea.wright@.ips-sendero.com#nospam> wrote in message
news:%23XbgujRtEHA.1040@.TK2MSFTNGP10.phx.gbl...
> Mine says SP3 as well - the a is missing...
> -- Andrea
> "Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
> news:ug0$JutsEHA.3320@.TK2MSFTNGP15.phx.gbl...
>
Issue with Installation of Service Pack 3a
All,
I successfully ran SQL Server Service Pack 3a on a machine that has two
instances of SQL Server. I ran the service pack against both instances. It
all appeared to run fine and I rebooted.
However, when I run the following select statement in Query Analyser:
select @.@.version
It is showing me:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
that the instances are at service pack 3a.
Did my service pack really run successfully? Is this a known issue?
Thanks,
Andrea Wright
andrea.wright@.ips-sendero.comHi Andrea,
The version of sql server you are running is 8.00.818 which is a hotfixed
version of SQL server later than than sp3 (which is version 8.00.760).
Actually the 818 version is coming with the public critical SQL server
security roll up fix MS03-031. I Expect you have installed this SQL server
security fix after you've installed sp3.
Regards,
Jago
"Andrea Wright" wrote:
> All,
> I successfully ran SQL Server Service Pack 3a on a machine that has two
> instances of SQL Server. I ran the service pack against both instances. It
> all appeared to run fine and I rebooted.
> However, when I run the following select statement in Query Analyser:
> select @.@.version
> It is showing me:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> that the instances are at service pack 3a.
> Did my service pack really run successfully? Is this a known issue?
> Thanks,
> Andrea Wright
> andrea.wright@.ips-sendero.com
>
>|||Jago,
Thanks for your quick response.
I installed the following in this order:
Hotfix that fixed the security issue and the Slammer virus (Microsoft SQL
Server 2000 - 8.00.679)
Service Pack 3 (not sure of the number this put it at)
Service Pack 3a (Microsoft SQL Server 2000 - 8.00.760)
I did not realize there was another hotfix, and I didn't apply one manually.
Is this one perhaps coming with Windows updates?
Thanks,
Andrea
"Jago" <Jago@.discussions.microsoft.com> wrote in message
news:B676216C-B1D0-4F05-A8A8-213BD997DC76@.microsoft.com...
> Hi Andrea,
> The version of sql server you are running is 8.00.818 which is a hotfixed
> version of SQL server later than than sp3 (which is version 8.00.760).
> Actually the 818 version is coming with the public critical SQL server
> security roll up fix MS03-031. I Expect you have installed this SQL server
> security fix after you've installed sp3.
> Regards,
> Jago
> "Andrea Wright" wrote:
>> All,
>> I successfully ran SQL Server Service Pack 3a on a machine that has two
>> instances of SQL Server. I ran the service pack against both instances.
>> It
>> all appeared to run fine and I rebooted.
>> However, when I run the following select statement in Query Analyser:
>> select @.@.version
>> It is showing me:
>> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
>> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
>> that the instances are at service pack 3a.
>> Did my service pack really run successfully? Is this a known issue?
>> Thanks,
>> Andrea Wright
>> andrea.wright@.ips-sendero.com
>>|||Hi Andre,
No was not coming with windows update
Jago
"Andrea Wright" wrote:
> Jago,
> Thanks for your quick response.
> I installed the following in this order:
> Hotfix that fixed the security issue and the Slammer virus (Microsoft SQL
> Server 2000 - 8.00.679)
> Service Pack 3 (not sure of the number this put it at)
> Service Pack 3a (Microsoft SQL Server 2000 - 8.00.760)
> I did not realize there was another hotfix, and I didn't apply one manually.
> Is this one perhaps coming with Windows updates?
> Thanks,
> Andrea
> "Jago" <Jago@.discussions.microsoft.com> wrote in message
> news:B676216C-B1D0-4F05-A8A8-213BD997DC76@.microsoft.com...
> > Hi Andrea,
> >
> > The version of sql server you are running is 8.00.818 which is a hotfixed
> > version of SQL server later than than sp3 (which is version 8.00.760).
> > Actually the 818 version is coming with the public critical SQL server
> > security roll up fix MS03-031. I Expect you have installed this SQL server
> > security fix after you've installed sp3.
> >
> > Regards,
> >
> > Jago
> >
> > "Andrea Wright" wrote:
> >
> >> All,
> >>
> >> I successfully ran SQL Server Service Pack 3a on a machine that has two
> >> instances of SQL Server. I ran the service pack against both instances.
> >> It
> >> all appeared to run fine and I rebooted.
> >>
> >> However, when I run the following select statement in Query Analyser:
> >> select @.@.version
> >>
> >> It is showing me:
> >> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> >>
> >> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> >> that the instances are at service pack 3a.
> >>
> >> Did my service pack really run successfully? Is this a known issue?
> >>
> >> Thanks,
> >> Andrea Wright
> >> andrea.wright@.ips-sendero.com
> >>
> >>
> >>
>
>|||To confirm whether you are on SP3a, run the following command.
select serverproperty('productLevel')
Andrea Wright wrote:
> All,
> I successfully ran SQL Server Service Pack 3a on a machine that has two
> instances of SQL Server. I ran the service pack against both instances. It
> all appeared to run fine and I rebooted.
> However, when I run the following select statement in Query Analyser:
> select @.@.version
> It is showing me:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> that the instances are at service pack 3a.
> Did my service pack really run successfully? Is this a known issue?
> Thanks,
> Andrea Wright
> andrea.wright@.ips-sendero.com
>|||"Jonathan Yong" <jyong@.someplace.net> wrote in message
news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
> To confirm whether you are on SP3a, run the following command.
> select serverproperty('productLevel')
And it should return... ? I "thought" I had SP3a - I definitely applied it
and received no errors. But I just ran this and it returns "SP3". When I
select @.@.version, I get 8.00.760.
>
> Andrea Wright wrote:
> > All,
> >
> > I successfully ran SQL Server Service Pack 3a on a machine that has two
> > instances of SQL Server. I ran the service pack against both instances.
It
> > all appeared to run fine and I rebooted.
> >
> > However, when I run the following select statement in Query Analyser:
> > select @.@.version
> >
> > It is showing me:
> > Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> >
> > It is not registering as Microsoft SQL Server 2000 - 8.00.760 to
indicate
> > that the instances are at service pack 3a.
> >
> > Did my service pack really run successfully? Is this a known issue?
> >
> > Thanks,
> > Andrea Wright
> > andrea.wright@.ips-sendero.com
> >
> >|||Mine says SP3 as well - the a is missing...
-- Andrea
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
news:ug0$JutsEHA.3320@.TK2MSFTNGP15.phx.gbl...
> "Jonathan Yong" <jyong@.someplace.net> wrote in message
> news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
>> To confirm whether you are on SP3a, run the following command.
>> select serverproperty('productLevel')
> And it should return... ? I "thought" I had SP3a - I definitely applied it
> and received no errors. But I just ran this and it returns "SP3". When I
> select @.@.version, I get 8.00.760.
>>
>> Andrea Wright wrote:
>> > All,
>> >
>> > I successfully ran SQL Server Service Pack 3a on a machine that has two
>> > instances of SQL Server. I ran the service pack against both
>> > instances.
> It
>> > all appeared to run fine and I rebooted.
>> >
>> > However, when I run the following select statement in Query Analyser:
>> > select @.@.version
>> >
>> > It is showing me:
>> > Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
>> >
>> > It is not registering as Microsoft SQL Server 2000 - 8.00.760 to
> indicate
>> > that the instances are at service pack 3a.
>> >
>> > Did my service pack really run successfully? Is this a known issue?
>> >
>> > Thanks,
>> > Andrea Wright
>> > andrea.wright@.ips-sendero.com
>> >
>> >
>|||AFIK, SQL Server doesn't differentiate between SP 3 and SP 3a with Select
@.@.version or any other method in the database itself. You can look in the
registry for the correct version. If you're running SQL Server, run regedit
and locate HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\CurrentVersion.
Then look at the CSDVersion value. It should be 8.00.761 for SP 3a,
8.00.760 for SP 3. There's also a file or two you can check for version
info in Windows Explorer, but I don't remember which ones off the top of my
head.
Thanks,
Michael C., MCDBA
"Andrea Wright" <andrea.wright@.ips-sendero.com#nospam> wrote in message
news:%23XbgujRtEHA.1040@.TK2MSFTNGP10.phx.gbl...
> Mine says SP3 as well - the a is missing...
> -- Andrea
> "Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
> news:ug0$JutsEHA.3320@.TK2MSFTNGP15.phx.gbl...
>> "Jonathan Yong" <jyong@.someplace.net> wrote in message
>> news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
>> To confirm whether you are on SP3a, run the following command.
>> select serverproperty('productLevel')
>> And it should return... ? I "thought" I had SP3a - I definitely applied
>> it
>> and received no errors. But I just ran this and it returns "SP3". When I
>> select @.@.version, I get 8.00.760.
>>
>>
>> Andrea Wright wrote:
>> > All,
>> >
>> > I successfully ran SQL Server Service Pack 3a on a machine that has
>> > two
>> > instances of SQL Server. I ran the service pack against both
>> > instances.
>> It
>> > all appeared to run fine and I rebooted.
>> >
>> > However, when I run the following select statement in Query Analyser:
>> > select @.@.version
>> >
>> > It is showing me:
>> > Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
>> >
>> > It is not registering as Microsoft SQL Server 2000 - 8.00.760 to
>> indicate
>> > that the instances are at service pack 3a.
>> >
>> > Did my service pack really run successfully? Is this a known issue?
>> >
>> > Thanks,
>> > Andrea Wright
>> > andrea.wright@.ips-sendero.com
>> >
>> >
>>
>
I successfully ran SQL Server Service Pack 3a on a machine that has two
instances of SQL Server. I ran the service pack against both instances. It
all appeared to run fine and I rebooted.
However, when I run the following select statement in Query Analyser:
select @.@.version
It is showing me:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
that the instances are at service pack 3a.
Did my service pack really run successfully? Is this a known issue?
Thanks,
Andrea Wright
andrea.wright@.ips-sendero.comHi Andrea,
The version of sql server you are running is 8.00.818 which is a hotfixed
version of SQL server later than than sp3 (which is version 8.00.760).
Actually the 818 version is coming with the public critical SQL server
security roll up fix MS03-031. I Expect you have installed this SQL server
security fix after you've installed sp3.
Regards,
Jago
"Andrea Wright" wrote:
> All,
> I successfully ran SQL Server Service Pack 3a on a machine that has two
> instances of SQL Server. I ran the service pack against both instances. It
> all appeared to run fine and I rebooted.
> However, when I run the following select statement in Query Analyser:
> select @.@.version
> It is showing me:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> that the instances are at service pack 3a.
> Did my service pack really run successfully? Is this a known issue?
> Thanks,
> Andrea Wright
> andrea.wright@.ips-sendero.com
>
>|||Jago,
Thanks for your quick response.
I installed the following in this order:
Hotfix that fixed the security issue and the Slammer virus (Microsoft SQL
Server 2000 - 8.00.679)
Service Pack 3 (not sure of the number this put it at)
Service Pack 3a (Microsoft SQL Server 2000 - 8.00.760)
I did not realize there was another hotfix, and I didn't apply one manually.
Is this one perhaps coming with Windows updates?
Thanks,
Andrea
"Jago" <Jago@.discussions.microsoft.com> wrote in message
news:B676216C-B1D0-4F05-A8A8-213BD997DC76@.microsoft.com...
> Hi Andrea,
> The version of sql server you are running is 8.00.818 which is a hotfixed
> version of SQL server later than than sp3 (which is version 8.00.760).
> Actually the 818 version is coming with the public critical SQL server
> security roll up fix MS03-031. I Expect you have installed this SQL server
> security fix after you've installed sp3.
> Regards,
> Jago
> "Andrea Wright" wrote:
>> All,
>> I successfully ran SQL Server Service Pack 3a on a machine that has two
>> instances of SQL Server. I ran the service pack against both instances.
>> It
>> all appeared to run fine and I rebooted.
>> However, when I run the following select statement in Query Analyser:
>> select @.@.version
>> It is showing me:
>> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
>> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
>> that the instances are at service pack 3a.
>> Did my service pack really run successfully? Is this a known issue?
>> Thanks,
>> Andrea Wright
>> andrea.wright@.ips-sendero.com
>>|||Hi Andre,
No was not coming with windows update
Jago
"Andrea Wright" wrote:
> Jago,
> Thanks for your quick response.
> I installed the following in this order:
> Hotfix that fixed the security issue and the Slammer virus (Microsoft SQL
> Server 2000 - 8.00.679)
> Service Pack 3 (not sure of the number this put it at)
> Service Pack 3a (Microsoft SQL Server 2000 - 8.00.760)
> I did not realize there was another hotfix, and I didn't apply one manually.
> Is this one perhaps coming with Windows updates?
> Thanks,
> Andrea
> "Jago" <Jago@.discussions.microsoft.com> wrote in message
> news:B676216C-B1D0-4F05-A8A8-213BD997DC76@.microsoft.com...
> > Hi Andrea,
> >
> > The version of sql server you are running is 8.00.818 which is a hotfixed
> > version of SQL server later than than sp3 (which is version 8.00.760).
> > Actually the 818 version is coming with the public critical SQL server
> > security roll up fix MS03-031. I Expect you have installed this SQL server
> > security fix after you've installed sp3.
> >
> > Regards,
> >
> > Jago
> >
> > "Andrea Wright" wrote:
> >
> >> All,
> >>
> >> I successfully ran SQL Server Service Pack 3a on a machine that has two
> >> instances of SQL Server. I ran the service pack against both instances.
> >> It
> >> all appeared to run fine and I rebooted.
> >>
> >> However, when I run the following select statement in Query Analyser:
> >> select @.@.version
> >>
> >> It is showing me:
> >> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> >>
> >> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> >> that the instances are at service pack 3a.
> >>
> >> Did my service pack really run successfully? Is this a known issue?
> >>
> >> Thanks,
> >> Andrea Wright
> >> andrea.wright@.ips-sendero.com
> >>
> >>
> >>
>
>|||To confirm whether you are on SP3a, run the following command.
select serverproperty('productLevel')
Andrea Wright wrote:
> All,
> I successfully ran SQL Server Service Pack 3a on a machine that has two
> instances of SQL Server. I ran the service pack against both instances. It
> all appeared to run fine and I rebooted.
> However, when I run the following select statement in Query Analyser:
> select @.@.version
> It is showing me:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> that the instances are at service pack 3a.
> Did my service pack really run successfully? Is this a known issue?
> Thanks,
> Andrea Wright
> andrea.wright@.ips-sendero.com
>|||"Jonathan Yong" <jyong@.someplace.net> wrote in message
news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
> To confirm whether you are on SP3a, run the following command.
> select serverproperty('productLevel')
And it should return... ? I "thought" I had SP3a - I definitely applied it
and received no errors. But I just ran this and it returns "SP3". When I
select @.@.version, I get 8.00.760.
>
> Andrea Wright wrote:
> > All,
> >
> > I successfully ran SQL Server Service Pack 3a on a machine that has two
> > instances of SQL Server. I ran the service pack against both instances.
It
> > all appeared to run fine and I rebooted.
> >
> > However, when I run the following select statement in Query Analyser:
> > select @.@.version
> >
> > It is showing me:
> > Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> >
> > It is not registering as Microsoft SQL Server 2000 - 8.00.760 to
indicate
> > that the instances are at service pack 3a.
> >
> > Did my service pack really run successfully? Is this a known issue?
> >
> > Thanks,
> > Andrea Wright
> > andrea.wright@.ips-sendero.com
> >
> >|||Mine says SP3 as well - the a is missing...
-- Andrea
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
news:ug0$JutsEHA.3320@.TK2MSFTNGP15.phx.gbl...
> "Jonathan Yong" <jyong@.someplace.net> wrote in message
> news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
>> To confirm whether you are on SP3a, run the following command.
>> select serverproperty('productLevel')
> And it should return... ? I "thought" I had SP3a - I definitely applied it
> and received no errors. But I just ran this and it returns "SP3". When I
> select @.@.version, I get 8.00.760.
>>
>> Andrea Wright wrote:
>> > All,
>> >
>> > I successfully ran SQL Server Service Pack 3a on a machine that has two
>> > instances of SQL Server. I ran the service pack against both
>> > instances.
> It
>> > all appeared to run fine and I rebooted.
>> >
>> > However, when I run the following select statement in Query Analyser:
>> > select @.@.version
>> >
>> > It is showing me:
>> > Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
>> >
>> > It is not registering as Microsoft SQL Server 2000 - 8.00.760 to
> indicate
>> > that the instances are at service pack 3a.
>> >
>> > Did my service pack really run successfully? Is this a known issue?
>> >
>> > Thanks,
>> > Andrea Wright
>> > andrea.wright@.ips-sendero.com
>> >
>> >
>|||AFIK, SQL Server doesn't differentiate between SP 3 and SP 3a with Select
@.@.version or any other method in the database itself. You can look in the
registry for the correct version. If you're running SQL Server, run regedit
and locate HKLM\Software\Microsoft\MSSQLServer\MSSQLServer\CurrentVersion.
Then look at the CSDVersion value. It should be 8.00.761 for SP 3a,
8.00.760 for SP 3. There's also a file or two you can check for version
info in Windows Explorer, but I don't remember which ones off the top of my
head.
Thanks,
Michael C., MCDBA
"Andrea Wright" <andrea.wright@.ips-sendero.com#nospam> wrote in message
news:%23XbgujRtEHA.1040@.TK2MSFTNGP10.phx.gbl...
> Mine says SP3 as well - the a is missing...
> -- Andrea
> "Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
> news:ug0$JutsEHA.3320@.TK2MSFTNGP15.phx.gbl...
>> "Jonathan Yong" <jyong@.someplace.net> wrote in message
>> news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
>> To confirm whether you are on SP3a, run the following command.
>> select serverproperty('productLevel')
>> And it should return... ? I "thought" I had SP3a - I definitely applied
>> it
>> and received no errors. But I just ran this and it returns "SP3". When I
>> select @.@.version, I get 8.00.760.
>>
>>
>> Andrea Wright wrote:
>> > All,
>> >
>> > I successfully ran SQL Server Service Pack 3a on a machine that has
>> > two
>> > instances of SQL Server. I ran the service pack against both
>> > instances.
>> It
>> > all appeared to run fine and I rebooted.
>> >
>> > However, when I run the following select statement in Query Analyser:
>> > select @.@.version
>> >
>> > It is showing me:
>> > Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
>> >
>> > It is not registering as Microsoft SQL Server 2000 - 8.00.760 to
>> indicate
>> > that the instances are at service pack 3a.
>> >
>> > Did my service pack really run successfully? Is this a known issue?
>> >
>> > Thanks,
>> > Andrea Wright
>> > andrea.wright@.ips-sendero.com
>> >
>> >
>>
>
Issue with Installation of Service Pack 3a
All,
I successfully ran SQL Server Service Pack 3a on a machine that has two
instances of SQL Server. I ran the service pack against both instances. It
all appeared to run fine and I rebooted.
However, when I run the following select statement in Query Analyser:
select @.@.version
It is showing me:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
that the instances are at service pack 3a.
Did my service pack really run successfully? Is this a known issue?
Thanks,
Andrea Wright
andrea.wright@.ips-sendero.comHi Andrea,
The version of sql server you are running is 8.00.818 which is a hotfixed
version of SQL server later than than sp3 (which is version 8.00.760).
Actually the 818 version is coming with the public critical SQL server
security roll up fix MS03-031. I Expect you have installed this SQL server
security fix after you've installed sp3.
Regards,
Jago
"Andrea Wright" wrote:
> All,
> I successfully ran SQL Server Service Pack 3a on a machine that has two
> instances of SQL Server. I ran the service pack against both instances.
It
> all appeared to run fine and I rebooted.
> However, when I run the following select statement in Query Analyser:
> select @.@.version
> It is showing me:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> that the instances are at service pack 3a.
> Did my service pack really run successfully? Is this a known issue?
> Thanks,
> Andrea Wright
> andrea.wright@.ips-sendero.com
>
>|||Jago,
Thanks for your quick response.
I installed the following in this order:
Hotfix that fixed the security issue and the Slammer virus (Microsoft SQL
Server 2000 - 8.00.679)
Service Pack 3 (not sure of the number this put it at)
Service Pack 3a (Microsoft SQL Server 2000 - 8.00.760)
I did not realize there was another hotfix, and I didn't apply one manually.
Is this one perhaps coming with Windows updates?
Thanks,
Andrea
"Jago" <Jago@.discussions.microsoft.com> wrote in message
news:B676216C-B1D0-4F05-A8A8-213BD997DC76@.microsoft.com...[vbcol=seagreen]
> Hi Andrea,
> The version of sql server you are running is 8.00.818 which is a hotfixed
> version of SQL server later than than sp3 (which is version 8.00.760).
> Actually the 818 version is coming with the public critical SQL server
> security roll up fix MS03-031. I Expect you have installed this SQL server
> security fix after you've installed sp3.
> Regards,
> Jago
> "Andrea Wright" wrote:
>|||Hi Andre,
No was not coming with windows update
Jago
"Andrea Wright" wrote:
> Jago,
> Thanks for your quick response.
> I installed the following in this order:
> Hotfix that fixed the security issue and the Slammer virus (Microsoft SQL
> Server 2000 - 8.00.679)
> Service Pack 3 (not sure of the number this put it at)
> Service Pack 3a (Microsoft SQL Server 2000 - 8.00.760)
> I did not realize there was another hotfix, and I didn't apply one manuall
y.
> Is this one perhaps coming with Windows updates?
> Thanks,
> Andrea
> "Jago" <Jago@.discussions.microsoft.com> wrote in message
> news:B676216C-B1D0-4F05-A8A8-213BD997DC76@.microsoft.com...
>
>|||To confirm whether you are on SP3a, run the following command.
select serverproperty('productLevel')
Andrea Wright wrote:
> All,
> I successfully ran SQL Server Service Pack 3a on a machine that has two
> instances of SQL Server. I ran the service pack against both instances.
It
> all appeared to run fine and I rebooted.
> However, when I run the following select statement in Query Analyser:
> select @.@.version
> It is showing me:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> that the instances are at service pack 3a.
> Did my service pack really run successfully? Is this a known issue?
> Thanks,
> Andrea Wright
> andrea.wright@.ips-sendero.com
>|||"Jonathan Yong" <jyong@.someplace.net> wrote in message
news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
> To confirm whether you are on SP3a, run the following command.
> select serverproperty('productLevel')
And it should return... ? I "thought" I had SP3a - I definitely applied it
and received no errors. But I just ran this and it returns "SP3". When I
select @.@.version, I get 8.00.760.
[vbcol=seagreen]
>
> Andrea Wright wrote:
It[vbcol=seagreen]
indicate[vbcol=seagreen]|||Mine says SP3 as well - the a is missing...
-- Andrea
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
news:ug0$JutsEHA.3320@.TK2MSFTNGP15.phx.gbl...
> "Jonathan Yong" <jyong@.someplace.net> wrote in message
> news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
> And it should return... ? I "thought" I had SP3a - I definitely applied it
> and received no errors. But I just ran this and it returns "SP3". When I
> select @.@.version, I get 8.00.760.
>
> It
> indicate
>|||AFIK, SQL Server doesn't differentiate between SP 3 and SP 3a with Select
@.@.version or any other method in the database itself. You can look in the
registry for the correct version. If you're running SQL Server, run regedit
and locate HKLM\Software\Microsoft\MSSQLServer\MSSQ
LServer\CurrentVersion.
Then look at the CSDVersion value. It should be 8.00.761 for SP 3a,
8.00.760 for SP 3. There's also a file or two you can check for version
info in Windows Explorer, but I don't remember which ones off the top of my
head.
Thanks,
Michael C., MCDBA
"Andrea Wright" <andrea.wright@.ips-sendero.com#nospam> wrote in message
news:%23XbgujRtEHA.1040@.TK2MSFTNGP10.phx.gbl...
> Mine says SP3 as well - the a is missing...
> -- Andrea
> "Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
> news:ug0$JutsEHA.3320@.TK2MSFTNGP15.phx.gbl...
>
I successfully ran SQL Server Service Pack 3a on a machine that has two
instances of SQL Server. I ran the service pack against both instances. It
all appeared to run fine and I rebooted.
However, when I run the following select statement in Query Analyser:
select @.@.version
It is showing me:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
that the instances are at service pack 3a.
Did my service pack really run successfully? Is this a known issue?
Thanks,
Andrea Wright
andrea.wright@.ips-sendero.comHi Andrea,
The version of sql server you are running is 8.00.818 which is a hotfixed
version of SQL server later than than sp3 (which is version 8.00.760).
Actually the 818 version is coming with the public critical SQL server
security roll up fix MS03-031. I Expect you have installed this SQL server
security fix after you've installed sp3.
Regards,
Jago
"Andrea Wright" wrote:
> All,
> I successfully ran SQL Server Service Pack 3a on a machine that has two
> instances of SQL Server. I ran the service pack against both instances.
It
> all appeared to run fine and I rebooted.
> However, when I run the following select statement in Query Analyser:
> select @.@.version
> It is showing me:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> that the instances are at service pack 3a.
> Did my service pack really run successfully? Is this a known issue?
> Thanks,
> Andrea Wright
> andrea.wright@.ips-sendero.com
>
>|||Jago,
Thanks for your quick response.
I installed the following in this order:
Hotfix that fixed the security issue and the Slammer virus (Microsoft SQL
Server 2000 - 8.00.679)
Service Pack 3 (not sure of the number this put it at)
Service Pack 3a (Microsoft SQL Server 2000 - 8.00.760)
I did not realize there was another hotfix, and I didn't apply one manually.
Is this one perhaps coming with Windows updates?
Thanks,
Andrea
"Jago" <Jago@.discussions.microsoft.com> wrote in message
news:B676216C-B1D0-4F05-A8A8-213BD997DC76@.microsoft.com...[vbcol=seagreen]
> Hi Andrea,
> The version of sql server you are running is 8.00.818 which is a hotfixed
> version of SQL server later than than sp3 (which is version 8.00.760).
> Actually the 818 version is coming with the public critical SQL server
> security roll up fix MS03-031. I Expect you have installed this SQL server
> security fix after you've installed sp3.
> Regards,
> Jago
> "Andrea Wright" wrote:
>|||Hi Andre,
No was not coming with windows update
Jago
"Andrea Wright" wrote:
> Jago,
> Thanks for your quick response.
> I installed the following in this order:
> Hotfix that fixed the security issue and the Slammer virus (Microsoft SQL
> Server 2000 - 8.00.679)
> Service Pack 3 (not sure of the number this put it at)
> Service Pack 3a (Microsoft SQL Server 2000 - 8.00.760)
> I did not realize there was another hotfix, and I didn't apply one manuall
y.
> Is this one perhaps coming with Windows updates?
> Thanks,
> Andrea
> "Jago" <Jago@.discussions.microsoft.com> wrote in message
> news:B676216C-B1D0-4F05-A8A8-213BD997DC76@.microsoft.com...
>
>|||To confirm whether you are on SP3a, run the following command.
select serverproperty('productLevel')
Andrea Wright wrote:
> All,
> I successfully ran SQL Server Service Pack 3a on a machine that has two
> instances of SQL Server. I ran the service pack against both instances.
It
> all appeared to run fine and I rebooted.
> However, when I run the following select statement in Query Analyser:
> select @.@.version
> It is showing me:
> Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> It is not registering as Microsoft SQL Server 2000 - 8.00.760 to indicate
> that the instances are at service pack 3a.
> Did my service pack really run successfully? Is this a known issue?
> Thanks,
> Andrea Wright
> andrea.wright@.ips-sendero.com
>|||"Jonathan Yong" <jyong@.someplace.net> wrote in message
news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
> To confirm whether you are on SP3a, run the following command.
> select serverproperty('productLevel')
And it should return... ? I "thought" I had SP3a - I definitely applied it
and received no errors. But I just ran this and it returns "SP3". When I
select @.@.version, I get 8.00.760.
[vbcol=seagreen]
>
> Andrea Wright wrote:
It[vbcol=seagreen]
indicate[vbcol=seagreen]|||Mine says SP3 as well - the a is missing...
-- Andrea
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
news:ug0$JutsEHA.3320@.TK2MSFTNGP15.phx.gbl...
> "Jonathan Yong" <jyong@.someplace.net> wrote in message
> news:eP150unsEHA.624@.TK2MSFTNGP09.phx.gbl...
> And it should return... ? I "thought" I had SP3a - I definitely applied it
> and received no errors. But I just ran this and it returns "SP3". When I
> select @.@.version, I get 8.00.760.
>
> It
> indicate
>|||AFIK, SQL Server doesn't differentiate between SP 3 and SP 3a with Select
@.@.version or any other method in the database itself. You can look in the
registry for the correct version. If you're running SQL Server, run regedit
and locate HKLM\Software\Microsoft\MSSQLServer\MSSQ
LServer\CurrentVersion.
Then look at the CSDVersion value. It should be 8.00.761 for SP 3a,
8.00.760 for SP 3. There's also a file or two you can check for version
info in Windows Explorer, but I don't remember which ones off the top of my
head.
Thanks,
Michael C., MCDBA
"Andrea Wright" <andrea.wright@.ips-sendero.com#nospam> wrote in message
news:%23XbgujRtEHA.1040@.TK2MSFTNGP10.phx.gbl...
> Mine says SP3 as well - the a is missing...
> -- Andrea
> "Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
> news:ug0$JutsEHA.3320@.TK2MSFTNGP15.phx.gbl...
>
Subscribe to:
Posts (Atom)