[NEWBIE] Replication with MSDE 2000

Hi everybody,
can someone help me about replication ?
I want to install msde2000 on two machines (identical) and keep database
updated like mirroring, so my users can connect to mirrored data if primary
server crashed down.
The two machines are in my LAN with their own IP number
Is it Possible ?
Thanks in advance and sorry of my poor knowledge of MSDE features
Merlinweb
Hi Merlinweb,
Merge replication goes close to doing what you want if you keep it
synchronizing constantly. There is some latency with the updates but that's
ok in many scenarios. It works very well when the servers are on the same
LAN. You will need to consider though, how to make schema changes, etc. as
that introduces quite a few issues.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"il_Leva" <il_levaMACIAO@.hotmail.com> wrote in message
news:41c97bf0$1@.x-privat.org...
> Hi everybody,
> can someone help me about replication ?
> I want to install msde2000 on two machines (identical) and keep database
> updated like mirroring, so my users can connect to mirrored data if
> primary
> server crashed down.
> The two machines are in my LAN with their own IP number
> Is it Possible ?
> Thanks in advance and sorry of my poor knowledge of MSDE features
> Merlinweb
>
|||"Greg Low [MVP]" <greglow@.lowell.com.au> ha scritto nel messaggio
news:uDw9mGI6EHA.2584@.TK2MSFTNGP10.phx.gbl...
> Hi Merlinweb,
> Merge replication goes close to doing what you want if you keep it
> synchronizing constantly. There is some latency with the updates but
that's
> ok in many scenarios. It works very well when the servers are on the same
> LAN. You will need to consider though, how to make schema changes, etc. as
> that introduces quite a few issues.
Thank you very much !
Now I go and search something useful on the net about merge replication.
Cheers
Merlinweb

[Newbie] Microsoft Analysis Server: Database not visible via remote XMLA

Hi,

I am trying to install the Adventure Works DW MS SQL Server 2005 Demo. I followed the instructions I found here and here (almost) to the letter. And lo and behold, I can actually see the Adventure Works DW Database in the Microsoft SQL Server Management Studio.

Moreover, when I execute the XMLA-Queries _in the SQL Server Management Studio_ to discover the datasources and then to list all catalogs, it displays all available catalogs just fine.

When I perform the exact same queries from a remote computer, only a previously installed Database (called "TestDB") is returned. No hint that Adventure Works could also exist.

I tried comparing the two databases (properties seem to be identical), but since I don't know anything about that "TestDB", it's really hard to see relevant differences.

Do I have to set certain access rights? I tried restarting the IIS service, but to no effect.

Now, above I stated that I followed the desciptions _almost_ to the letter. The step I could not reproduce was in the second link. It stated that I had to create an "Application Pool", but when I browsed to the IIS Node in the Computer Management console, I expanded it, but could not find "Application Pool" anywhere near it. So I did not create a new application pool -- it may, however, very well be that an Application Pool already existed.

Any ideas as to where I might look for errors?
Thanks in advance!
Philipp

Are you connecting using the same account? If not you would need to add the account to a role in Adventure Works.

The application pools only exist in IIS 6 which comes with Win2003 server, so if you are using WinXP or Win2000 you will not have application pools.

You could run SQL profiler and see what account SSAS is seeing when you ask it for a list of catalogs.

|||Thanks. Adding my user to a rule did the trick.

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

trying to install sql server2005 on a windows 2003 server box.

getting msg below at the sql server . i looked at other posts on trying to uninstall SQL Native Access Client and norton antivirus. i could never find the snac on the add - remove programs and this server does not have a virus protection program yet.

here's the history of the installs on the server:

wanted to test a 2005 upgrade so:

1) installed sql server 2000 then sp4 then restored some databases to it - all OK

2) tried to upgrade to sql 2005 but ran into problems and left it at that.

had a disk drive crash on the d drive so lost the installs but not the operating system

when the drive was replaced, left alone for a while

then wanted to test a straight 2005 install

1) removed the broken 2005 attempt

2) removed the 2000

3) installed 2005 and got the error on the subject line:

TITLE: Microsoft SQL Server 2005 Setup

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

i've gone through as many of the forums that i can and have tried several things - like uninstalling 2005 and installing pieces and parts but but nothing seems to work.

Thanks!

Dan <><

It sounds like the SNAC version you have might be corrupt or incompatible.

Go to Add or Remove Programs and find the listing for "Microsoft SQL Native Client". Remove this component.

Then try the install again.

Michelle

|||

Thank you so much for replying. last attempt was to install just the sql server commonent - no others like analysis services or integration services.

i looked at the add / remove programs both before, during and after the sql server database services failed attempt and the add/remove has never shown a program called MS sql native access client (SNAC).

when i start the install, the installing prerequisites window shows the two components that will be installed: snac and the sql server 2005 setup support files. the snac goes to a green arrow almost immediately while the 2005 setup files takes a few seconds. i dont know if that helps or not.

the add remove programs just has:

microsoft .net framwork 2.0|||

It definatel looks like the problems is the "Microsoft SQL Server Native Client" layer. At this point your machine thinks that it is already installed but the install is broken.

Follow the directions in the following article to clean up the machine and then try again.

http://support.microsoft.com/kb/909967

Michelle

|||

uninstall manually - did the following (shows issues with some of the directions)

it said to delete the local security groups. but i never could figure out how to do. the article it mensions didnt (at least to me) show how to delete. so i just went on|||

i went out to the website and downloaded the .msi file for snac. it was slightly different from the .msi that came on the DVD (3511k vs 3516k).

the dvd version when i clicked on the msi file just returned me back to windows explorer.

the snac from microsoft's website executed and finally installed the snac.

the install worked perfectly after that.

thanks for your help

|||

Actually that was a good work around as downloading a newer version would have forced the install to run again where as in the previous case it was failing quickly becuase it thought it was laready installed.

Glad you got you machine back.

Michelle

|||

Hi,

I've been handling SQL Server upgrades for many years. The most dangerous path for an upgrade is to directly upgrade 2000 to 2005 (or 7.0 to 2000). That's because you create the risk of destroying the databases on the existing server and causing data loss.

The best approach embraces the fact that we typically upgrade a windows server when the mfg warranty on the hardware has expired. So, you have a new box and windows server. If you don't, the store the backups on another resource (disk, tape, flash drive, etc...) and copy from or restore from that resource. Rebuild the Windows server or uninstall SQL Server 2000. (I would have fresh windows to insure the best chance of success.)

Install SQL 2005 & configure on the new W03 SP1 server. migrate the users. (this worked easily with 2K but MS has hosed that functionality in 2005 from what I can see; you must use a script they provided that is flaky. You will need to manually create the users it fails to migrate.) Backup the dbs on 2K, shut down 2K on the old machine and restore the dbs to 2005. associate the users with the logins.

Now you have a fullly upgraded database server and your databases are unhosed. This may not be elegant but it guarantees the MS upgrade process won't destroy your databases or bring down your business for days.

If you have a completely hosed system, then rebuild the system (and the drives) and follow the steps above to a successful conclusion.

z.

[INSTALL SQL SERVER] GOT A WARNING MESSAGE

[Microsoft SQL server 2000 standard edition server component is not
supported ont this operation system
Only client components will be avaiable for installation ]
my OS is winXP professional edition.
Anything wrong ?
please help
It is not possible to install SQL Server (the server edition) on to a =
desktop OS such as XP Pro. =20
You do have a few options if you need the DBMS installed on your =
computer (for example for development/testing). You can install the =
Personal Edition or the Developer Edition of SQL Server to your desktop =
machine.
--=20
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =
news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
>=20
> my OS is winXP professional edition.
> Anything wrong ?
> please help
>=20
>
|||That's mean I can install to window server2000 but not XP Pro ?
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
It is not possible to install SQL Server (the server edition) on to a
desktop OS such as XP Pro.
You do have a few options if you need the DBMS installed on your computer
(for example for development/testing). You can install the Personal Edition
or the Developer Edition of SQL Server to your desktop machine.
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message
news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
> my OS is winXP professional edition.
> Anything wrong ?
> please help
>
|||> That's mean I can install to window server2000 but not XP Pro ?
That is the expected (and correct) behavior.

> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
This is a true statement

> Only client components will be avaiable for installation ]
Also a true statement

> my OS is winXP professional edition.
This is your problem. The server editions (Standard and Enterprise) of =
SQL Server do not install on to desktop operating systems. If you want =
to install SQL Server onto your desktop operating system you will need =
to install the Personal Edition, the Developer Edition, or a trial =
edition.

> Anything wrong ?
You are trying to install SQL Server onto an operating system that it =
does not install on.
--=20
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =
news:%23b76DCPPEHA.3128@.TK2MSFTNGP10.phx.gbl...
> That's mean I can install to window server2000 but not XP Pro ?
>=20
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
> news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
> It is not possible to install SQL Server (the server edition) on to a
> desktop OS such as XP Pro.
>=20
> You do have a few options if you need the DBMS installed on your =
computer
> (for example for development/testing). You can install the Personal =
Edition
> or the Developer Edition of SQL Server to your desktop machine.
>=20
> --=20
> Keith
>=20
>=20
> "Agnes" <agnes@.dynamictech.com.hk> wrote in message
> news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
>=20
>

[INSTALL SQL SERVER] GOT A WARNING MESSAGE

[Microsoft SQL server 2000 standard edition server component is not
supported ont this operation system
Only client components will be avaiable for installation ]
my OS is winXP professional edition.
Anything wrong '
please helpIt is not possible to install SQL Server (the server edition) on to a =
desktop OS such as XP Pro. =20
You do have a few options if you need the DBMS installed on your =
computer (for example for development/testing). You can install the =
Personal Edition or the Developer Edition of SQL Server to your desktop =
machine.
--=20
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =
news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
>=20
> my OS is winXP professional edition.
> Anything wrong '
> please help
>=20
>|||That's mean I can install to window server2000 but not XP Pro '
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
It is not possible to install SQL Server (the server edition) on to a
desktop OS such as XP Pro.
You do have a few options if you need the DBMS installed on your computer
(for example for development/testing). You can install the Personal Edition
or the Developer Edition of SQL Server to your desktop machine.
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message
news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
> my OS is winXP professional edition.
> Anything wrong '
> please help
>|||> That's mean I can install to window server2000 but not XP Pro '
That is the expected (and correct) behavior.

> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
This is a true statement

> Only client components will be avaiable for installation ]
Also a true statement

> my OS is winXP professional edition.
This is your problem. The server editions (Standard and Enterprise) of =
SQL Server do not install on to desktop operating systems. If you want =
to install SQL Server onto your desktop operating system you will need =
to install the Personal Edition, the Developer Edition, or a trial =
edition.

> Anything wrong '
You are trying to install SQL Server onto an operating system that it =
does not install on.
--=20
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =
news:%23b76DCPPEHA.3128@.TK2MSFTNGP10.phx.gbl...
> That's mean I can install to window server2000 but not XP Pro '
>=20
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
> news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
> It is not possible to install SQL Server (the server edition) on to a
> desktop OS such as XP Pro.
>=20
> You do have a few options if you need the DBMS installed on your =
computer
> (for example for development/testing). You can install the Personal =
Edition
> or the Developer Edition of SQL Server to your desktop machine.
>=20
> --=20
> Keith
>=20
>=20
> "Agnes" <agnes@.dynamictech.com.hk> wrote in message
> news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
>=20
>

[INSTALL SQL SERVER] GOT A WARNING MESSAGE

[Microsoft SQL server 2000 standard edition server component is not
supported ont this operation system
Only client components will be avaiable for installation ]
my OS is winXP professional edition.
Anything wrong '
please helpIt is not possible to install SQL Server (the server edition) on to a =desktop OS such as XP Pro.
You do have a few options if you need the DBMS installed on your =computer (for example for development/testing). You can install the =Personal Edition or the Developer Edition of SQL Server to your desktop =machine.
-- Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
> > my OS is winXP professional edition.
> Anything wrong '
> please help
> >|||That's mean I can install to window server2000 but not XP Pro '
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
It is not possible to install SQL Server (the server edition) on to a
desktop OS such as XP Pro.
You do have a few options if you need the DBMS installed on your computer
(for example for development/testing). You can install the Personal Edition
or the Developer Edition of SQL Server to your desktop machine.
--
Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message
news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
> Only client components will be avaiable for installation ]
> my OS is winXP professional edition.
> Anything wrong '
> please help
>|||> That's mean I can install to window server2000 but not XP Pro '
That is the expected (and correct) behavior.
> [Microsoft SQL server 2000 standard edition server component is not
> supported ont this operation system
This is a true statement
> Only client components will be avaiable for installation ]
Also a true statement
> my OS is winXP professional edition.
This is your problem. The server editions (Standard and Enterprise) of =SQL Server do not install on to desktop operating systems. If you want =to install SQL Server onto your desktop operating system you will need =to install the Personal Edition, the Developer Edition, or a trial =edition.
> Anything wrong '
You are trying to install SQL Server onto an operating system that it =does not install on.
-- Keith
"Agnes" <agnes@.dynamictech.com.hk> wrote in message =news:%23b76DCPPEHA.3128@.TK2MSFTNGP10.phx.gbl...
> That's mean I can install to window server2000 but not XP Pro '
> > "Keith Kratochvil" <sqlguy.back2u@.comcast.net> ?
> news:OCgeK4OPEHA.3124@.TK2MSFTNGP12.phx.gbl ?...
> It is not possible to install SQL Server (the server edition) on to a
> desktop OS such as XP Pro.
> > You do have a few options if you need the DBMS installed on your =computer
> (for example for development/testing). You can install the Personal =Edition
> or the Developer Edition of SQL Server to your desktop machine.
> > -- > Keith
> > > "Agnes" <agnes@.dynamictech.com.hk> wrote in message
> news:eJd9rxOPEHA.1340@.TK2MSFTNGP12.phx.gbl...
> > [Microsoft SQL server 2000 standard edition server component is not
> > supported ont this operation system
> > Only client components will be avaiable for installation ]
> >
> > my OS is winXP professional edition.
> > Anything wrong '
> > please help
> >
> >
> >

[HELP] The right version

Hi Everyone !
I need an advice :
i have a Intel Xeon 2,8 Ghz with 4 Gb RAM.
I would like to install the 64-bit version of SQL Server 2000.
Which Windows server do i need ?
Windows 2000 Advanced server is enough ?
or Windows 2003 server ?
I'm confused because the only 64-bit Windows 2003 server available is the
one optimized for Itanium processors... thank you
You have a 32-bit machine. You can only install 32-bit operating systems
and applications on the machine you described.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Danny" <dannyniceOnlyWithWhoWillRespectMe@.hotmail.com> wrote in message
news:2h1lefF84oo0U1@.uni-berlin.de...
> Hi Everyone !
> I need an advice :
> i have a Intel Xeon 2,8 Ghz with 4 Gb RAM.
> I would like to install the 64-bit version of SQL Server 2000.
> Which Windows server do i need ?
> Windows 2000 Advanced server is enough ?
> or Windows 2003 server ?
> I'm confused because the only 64-bit Windows 2003 server available is the
> one optimized for Itanium processors... thank you
>
>
|||> i have a Intel Xeon 2,8 Ghz with 4 Gb RAM.
> I would like to install the 64-bit version of SQL Server 2000.
Why? You need 64-bit hardware (e.g. Itanium processors!) to run 64-bit
software (!).
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/

[HELP] The right version

Hi Everyone !
I need an advice :
i have a Intel Xeon 2,8 Ghz with 4 Gb RAM.
I would like to install the 64-bit version of SQL Server 2000.
Which Windows server do i need ?
Windows 2000 Advanced server is enough ?
or Windows 2003 server ?
I'm confused because the only 64-bit Windows 2003 server available is the
one optimized for Itanium processors... thank you You have a 32-bit machine. You can only install 32-bit operating systems
and applications on the machine you described.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Danny" < dannyniceOnlyWithWhoWillRespectMe@.hotmai
l.com> wrote in message
news:2h1lefF84oo0U1@.uni-berlin.de...
> Hi Everyone !
> I need an advice :
> i have a Intel Xeon 2,8 Ghz with 4 Gb RAM.
> I would like to install the 64-bit version of SQL Server 2000.
> Which Windows server do i need ?
> Windows 2000 Advanced server is enough ?
> or Windows 2003 server ?
> I'm confused because the only 64-bit Windows 2003 server available is the
> one optimized for Itanium processors... thank you
>
>|||> i have a Intel Xeon 2,8 Ghz with 4 Gb RAM.
> I would like to install the 64-bit version of SQL Server 2000.
Why? You need 64-bit hardware (e.g. Itanium processors!) to run 64-bit
software (!).
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/

[HELP] The right version

Hi Everyone !
I need an advice :
i have a Intel Xeon 2,8 Ghz with 4 Gb RAM.
I would like to install the 64-bit version of SQL Server 2000.
Which Windows server do i need ?
Windows 2000 Advanced server is enough ?
or Windows 2003 server ?
I'm confused because the only 64-bit Windows 2003 server available is the
one optimized for Itanium processors... thank you :)You have a 32-bit machine. You can only install 32-bit operating systems
and applications on the machine you described.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Danny" <dannyniceOnlyWithWhoWillRespectMe@.hotmail.com> wrote in message
news:2h1lefF84oo0U1@.uni-berlin.de...
> Hi Everyone !
> I need an advice :
> i have a Intel Xeon 2,8 Ghz with 4 Gb RAM.
> I would like to install the 64-bit version of SQL Server 2000.
> Which Windows server do i need ?
> Windows 2000 Advanced server is enough ?
> or Windows 2003 server ?
> I'm confused because the only 64-bit Windows 2003 server available is the
> one optimized for Itanium processors... thank you :)
>
>|||> i have a Intel Xeon 2,8 Ghz with 4 Gb RAM.
> I would like to install the 64-bit version of SQL Server 2000.
Why? You need 64-bit hardware (e.g. Itanium processors!) to run 64-bit
software (!).
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/

[help] installation problems with sql server express 2005

hello everybody
I've downloaded a free version of ms sql server express 2005
and while I lauch the install file, I Have a bug :
Something like :
"you don't have write and read permission" - conctact administator
but i'm logged on a administator session

if anyone can help me ..
thnx in advance ..
hzben

Hi,

Ensure you have Read & Write permission on the folder/drive you are trying to install SQL Server , i.e. Program Files folder!!! www.windowsecurity.com/articles/Understanding-Windows-NTFS-Permissions.html FYI.

Hemantgiri S. Goswami

|||thank you for this reply
Do i can export a sql 2000 database to sql 2005 express only with a .sql file or do i need the .mdf and .ldf files of my old database ?
I need to export only the structure (tables ,columns and triggers) of my database to sql express 2005 .
have a nice day !!
hzben|||

Hi hzben,

you can export the structure of your database with your .sql file (Script of Database Objects) and for that you don't need .mdf/.ldf files. But in case you wants to attach your database to sql server you require .mdf and .ldf.

HTH

Hemantgiri S. Goswami

@@Version not updating

Greetings,
I recently installed Service Pack 4 on SQL 2000. The install went
smooth with no errors and a message at the end stating the install
completed successfully. I rebooted the server (Windows Server '03) and
tried to check the @.@.Version global variable but it still lists only
Service Pack 1.
Could it be that SP4 didn't install? Or is it more likely something
else is preventing the @.@.Version from updating?
Thanks in advance,
BenHi Ben
What do you get from
SELECT SERVERPROPERTY('ProductLevel')
HTH
Kalen Delaney, SQL Server MVP
"sullins602" <ben.sullins@.gmail.com> wrote in message
news:1152814872.081466.270730@.s13g2000cwa.googlegroups.com...
> Greetings,
> I recently installed Service Pack 4 on SQL 2000. The install went
> smooth with no errors and a message at the end stating the install
> completed successfully. I rebooted the server (Windows Server '03) and
> tried to check the @.@.Version global variable but it still lists only
> Service Pack 1.
> Could it be that SP4 didn't install? Or is it more likely something
> else is preventing the @.@.Version from updating?
> Thanks in advance,
> Ben
>|||Hi Ben,
Looks like @.@.version does not show the SQL Server service pack number but a
version number. Check for a number like 8.00.2039. Probably the service pack
listed is for the operating system.
Hope this helps,
Ben Nevarez, MCDBA, OCP
Database Administrator
"sullins602" wrote:

> Greetings,
> I recently installed Service Pack 4 on SQL 2000. The install went
> smooth with no errors and a message at the end stating the install
> completed successfully. I rebooted the server (Windows Server '03) and
> tried to check the @.@.Version global variable but it still lists only
> Service Pack 1.
> Could it be that SP4 didn't install? Or is it more likely something
> else is preventing the @.@.Version from updating?
> Thanks in advance,
> Ben
>|||Thats it! I was looking at the service pack for the OS not the
database. Thanks for your help fellas...
-ben

@@Version not updating

Greetings,
I recently installed Service Pack 4 on SQL 2000. The install went
smooth with no errors and a message at the end stating the install
completed successfully. I rebooted the server (Windows Server '03) and
tried to check the @.@.Version global variable but it still lists only
Service Pack 1.
Could it be that SP4 didn't install? Or is it more likely something
else is preventing the @.@.Version from updating?
Thanks in advance,
BenHi Ben
What do you get from
SELECT SERVERPROPERTY('ProductLevel')
--
HTH
Kalen Delaney, SQL Server MVP
"sullins602" <ben.sullins@.gmail.com> wrote in message
news:1152814872.081466.270730@.s13g2000cwa.googlegroups.com...
> Greetings,
> I recently installed Service Pack 4 on SQL 2000. The install went
> smooth with no errors and a message at the end stating the install
> completed successfully. I rebooted the server (Windows Server '03) and
> tried to check the @.@.Version global variable but it still lists only
> Service Pack 1.
> Could it be that SP4 didn't install? Or is it more likely something
> else is preventing the @.@.Version from updating?
> Thanks in advance,
> Ben
>|||Hi Ben,
Looks like @.@.version does not show the SQL Server service pack number but a
version number. Check for a number like 8.00.2039. Probably the service pack
listed is for the operating system.
Hope this helps,
Ben Nevarez, MCDBA, OCP
Database Administrator
"sullins602" wrote:
> Greetings,
> I recently installed Service Pack 4 on SQL 2000. The install went
> smooth with no errors and a message at the end stating the install
> completed successfully. I rebooted the server (Windows Server '03) and
> tried to check the @.@.Version global variable but it still lists only
> Service Pack 1.
> Could it be that SP4 didn't install? Or is it more likely something
> else is preventing the @.@.Version from updating?
> Thanks in advance,
> Ben
>|||Thats it! I was looking at the service pack for the OS not the
database. Thanks for your help fellas...
-ben