Determine when a Service Pack was applied?

We are running SQL Server 2000 with SP3. Is there a way to determine
the date the last service pack was applied?
Thanks
Randy K wrote:
> We are running SQL Server 2000 with SP3. Is there a way to determine
> the date the last service pack was applied?
> Thanks
You could look in the error log and see when that version was first
booted (assuming they have no been overwritten). Use SQL EM or use the
undocumented procedures from Query Analyzer:
Exec sp_enumerrorlogs -- returns each error log and it's Archive #
Exec sp_readerrorlog -- no parameter for current log or pass in archive
# to read another log
David Gugick - SQL Server MVP
Quest Software
|||Look for the Sqlsp.log in your Windows directory. It's the logfile from
your last Service pack installation.
Markus

Determine when a Service Pack was applied?

We are running SQL Server 2000 with SP3. Is there a way to determine
the date the last service pack was applied?
ThanksRandy K wrote:
> We are running SQL Server 2000 with SP3. Is there a way to determine
> the date the last service pack was applied?
> Thanks
You could look in the error log and see when that version was first
booted (assuming they have no been overwritten). Use SQL EM or use the
undocumented procedures from Query Analyzer:
Exec sp_enumerrorlogs -- returns each error log and it's Archive #
Exec sp_readerrorlog -- no parameter for current log or pass in archive
# to read another log
David Gugick - SQL Server MVP
Quest Software|||Look for the Sqlsp.log in your Windows directory. It's the logfile from
your last Service pack installation.
Markus

Determine when a Service Pack was applied?

We are running SQL Server 2000 with SP3. Is there a way to determine
the date the last service pack was applied?
ThanksRandy K wrote:
> We are running SQL Server 2000 with SP3. Is there a way to determine
> the date the last service pack was applied?
> Thanks
You could look in the error log and see when that version was first
booted (assuming they have no been overwritten). Use SQL EM or use the
undocumented procedures from Query Analyzer:
Exec sp_enumerrorlogs -- returns each error log and it's Archive #
Exec sp_readerrorlog -- no parameter for current log or pass in archive
# to read another log
David Gugick - SQL Server MVP
Quest Software|||Look for the Sqlsp.log in your Windows directory. It's the logfile from
your last Service pack installation.
Markus

determine the SP level of a client install?

Hello,
How can I tell what service pack has been installed on a local (non-server) client installation of SQL Server 2000?
I'd appreciate any feedback
Thanks,
John
Have you looked at Help | About within Query Analyzer?
--=20
Keith
"John P" <John P@.discussions.microsoft.com> wrote in message =
news:6A79F645-CBF8-4123-8FC8-CC0A8952A7F6@.microsoft.com...
> Hello,
>=20
> How can I tell what service pack has been installed on a local =
(non-server) client installation of SQL Server 2000?
>=20
> I'd appreciate any feedback
>=20
> Thanks,
>=20
> John
|||ahh...why didn't I think of that?! I tried that in Enterprise Manager but noticed it was MMC not SQL so I gave up!
Thanks Keith!
"Keith Kratochvil" wrote:

> Have you looked at Help | About within Query Analyzer?
> --
> Keith
>
> "John P" <John P@.discussions.microsoft.com> wrote in message news:6A79F645-CBF8-4123-8FC8-CC0A8952A7F6@.microsoft.com...
>
|||Yeah, Help | About within EM gives information about MMC, not about the =
specific snap in.
--=20
Keith
"John P" <JohnP@.discussions.microsoft.com> wrote in message =
news:62578D1D-7A60-440B-99A4-5B8B774A6E73@.microsoft.com...
> ahh...why didn't I think of that?! I tried that in Enterprise Manager =
but noticed it was MMC not SQL so I gave up![vbcol=seagreen]
>=20
> Thanks Keith!
>=20
> "Keith Kratochvil" wrote:
>=20
news:6A79F645-CBF8-4123-8FC8-CC0A8952A7F6@.microsoft.com...[vbcol=seagreen]
(non-server) client installation of SQL Server 2000?[vbcol=seagreen]

Determine service pack version of Analysis Services using AMO

Hi,

Our product uses features that require Analysis Services SP2 to be installed. How can I tell if an Analysis Services server is running SP2 or higher using Analysis Services Management Objects (AMO)? I'm not concerned about the Operating System service pack edition, I'm concerned about the SP version of Analysis Services.

Thanks.

Figured it out. Use the Version property off the Server object.

Server svr = new Server();

svr.Connect(serverName);

Version minASVersion = new Version(MIN_AS_SERVICES_VERSION);

Version serverVersion = new Version(svr.Version);

if (serverVersion < minASVersion)

{

// error

}

|||

You can get this using ADOMD too:

http://geekswithblogs.net/darrengosbell/archive/2007/07/14/SSAS-Detecting-the-version-of-SSAS-on-a-given-server.aspx

sql

Determine if Service Pack 1 is installed on SQL 2005 ?

How can I determine if SP1 is installed for SQL Server 2005?

TIA

select @.@.version

Frank

|||

Since this is the SSIS forum, I thought a SSIS specific method my be usefull. Since you don't have to install the DB engine, you may just have SSIS installed, so the normal @.@.VERSION does not work anymore. One method is to check the File Version of the SSIS Service, C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.exe

Right-click the file and select Properties. On the Version tab check the File Version property. RTM shows 9.00.1399.00, SP1 shows 9.00.2047.00

Strictly speaking the MsDtsSrvr.exe may not always be updated with a service pack or patch, so the version may reflect an older level. An alternative method is to check the registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\DTS\Setup, values Version and PatchLevel give the service pack and hotfix level respectively. The RTM values are both 9.00.1399.06, and SP1 is 9.1.2047.00. Note the 9.1 rather than 9.0 for the SP1 version.

|||Actually "select @.@.version" works well in 2005.

Detecting Feature Pack components on a SQL Server server

We have a product that uses, and will bootstrap, several of the feature pack components when it is installed (xmo, MSOLAP9, etc). However, if our product is installed on a machine that has SQL Server 2005 already installed, all of the feature pack components will have been installed as part of the server install, so we don't want to bootstrap them in that case. Is there a good way to detect this case? Clearly, simply checking that the feature pack MSI hasn't been installed isn't good enough, since SQL Server has its own MSIs that are different from the FP MSIs.

Can you try to check the registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server or use WMI to detect the SQL Server 2005 components? WMI should be a better choice.

|||

I'm not sure that would be wise in that case, since if SQL Server 2005 was removed it would break your application. You are best off to install the MSIs all the time, and to use the product ref-counting mechanism available in the redists to make sure they won't be removed unless your application has been. This is done by running the redist MSIs with the APPGUID property set on the command line, with the value of the property being the product code of your application that is being installed. What this will do is block the user from uninstalling those applications until your product has been removed first.