Determine what version of RS is insalled

How do you determine what version of Reporting Services is installed int the DB and Web server ( I have the DB on a different server than the Web server)

Thanks

Try typing
http://localhost/Reportserver

Determine what ver/SP is installed for Reporting Services

How can you tell what version of Reporting Services is installed?Just run the url http://localhost/ReportServer or
http://<hostname>/ReportServer|||That is where to look, however I didn't know what the numbers meant. I
found this in another thread:
base install = 743
sp1 = 878
sp2 = 1042|||If you run the url. at the bottom it will display the version information
like following
Microsoft SQL Server Reporting Services Version 8.00.1038.00sql

Determine what User Account SQL Server is running under

(MS SQL 2000)
Is there a way to determine what network user account SQL Server is
installed and running under? More importantly, can I easily change it?
Thanks!If you have permissions to the server have a look in Control Panel /
Services / MSSQLServer / Logon Tab
It can be easily changed but you do need to stop/start the services for it
to take effect
--
HTH. Ryan
"D. Shane Fowlkes" <shanefowlkes@.h-o-t-m-a-i-l.com> wrote in message
news:uLoxF9TEGHA.1508@.TK2MSFTNGP15.phx.gbl...
> (MS SQL 2000)
> Is there a way to determine what network user account SQL Server is
> installed and running under? More importantly, can I easily change it?
> Thanks!
>|||Thanks! That was pretty easy.
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23zgi8AUEGHA.2724@.TK2MSFTNGP12.phx.gbl...
> If you have permissions to the server have a look in Control Panel /
> Services / MSSQLServer / Logon Tab
> It can be easily changed but you do need to stop/start the services for it
> to take effect
> --
> HTH. Ryan
>
> "D. Shane Fowlkes" <shanefowlkes@.h-o-t-m-a-i-l.com> wrote in message
> news:uLoxF9TEGHA.1508@.TK2MSFTNGP15.phx.gbl...
>> (MS SQL 2000)
>> Is there a way to determine what network user account SQL Server is
>> installed and running under? More importantly, can I easily change it?
>> Thanks!
>>
>|||Hi,
The proper method to change the account is via the Enterprise Manager or you
have to grant the new account some additional permissions on the server. I do
not remember all of the permissions, but they include 'act as part of os',
'run as service', etc.
If the account is changed via the EM, all of the required permisions are
automatically granted.
hth
DeeJay Puar
MCDBA
"D. Shane Fowlkes" wrote:
> Thanks! That was pretty easy.
>
> "Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
> news:%23zgi8AUEGHA.2724@.TK2MSFTNGP12.phx.gbl...
> > If you have permissions to the server have a look in Control Panel /
> > Services / MSSQLServer / Logon Tab
> >
> > It can be easily changed but you do need to stop/start the services for it
> > to take effect
> >
> > --
> > HTH. Ryan
> >
> >
> > "D. Shane Fowlkes" <shanefowlkes@.h-o-t-m-a-i-l.com> wrote in message
> > news:uLoxF9TEGHA.1508@.TK2MSFTNGP15.phx.gbl...
> >> (MS SQL 2000)
> >>
> >> Is there a way to determine what network user account SQL Server is
> >> installed and running under? More importantly, can I easily change it?
> >>
> >> Thanks!
> >>
> >>
> >
> >
>
>|||Thanks again.
"DeeJay Puar" <DeeJayPuar@.discussions.microsoft.com> wrote in message
news:5881C956-4A72-4868-A3BC-1E3907C3667E@.microsoft.com...
> Hi,
> The proper method to change the account is via the Enterprise Manager or
> you
> have to grant the new account some additional permissions on the server. I
> do
> not remember all of the permissions, but they include 'act as part of os',
> 'run as service', etc.
> If the account is changed via the EM, all of the required permisions are
> automatically granted.
> hth
> DeeJay Puar
> MCDBA
> "D. Shane Fowlkes" wrote:
>> Thanks! That was pretty easy.
>>
>> "Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
>> news:%23zgi8AUEGHA.2724@.TK2MSFTNGP12.phx.gbl...
>> > If you have permissions to the server have a look in Control Panel /
>> > Services / MSSQLServer / Logon Tab
>> >
>> > It can be easily changed but you do need to stop/start the services for
>> > it
>> > to take effect
>> >
>> > --
>> > HTH. Ryan
>> >
>> >
>> > "D. Shane Fowlkes" <shanefowlkes@.h-o-t-m-a-i-l.com> wrote in message
>> > news:uLoxF9TEGHA.1508@.TK2MSFTNGP15.phx.gbl...
>> >> (MS SQL 2000)
>> >>
>> >> Is there a way to determine what network user account SQL Server is
>> >> installed and running under? More importantly, can I easily change
>> >> it?
>> >>
>> >> Thanks!
>> >>
>> >>
>> >
>> >
>>

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.

Determine if MSDE or SQL server is installed

During an install of my software i like to know if MSDE or SQL Server is
installed.
Is there any way i can tell this from the registry.
--
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.529 / Virus Database: 324 - Release Date: 16/10/2003Jeff,
Check the existance of following registry key. (It is applicable to MSDE as well as other editions
of SQL)
HKLM\Software\Microsoft\Microsoft SQL Server
--
- Vishalsql

Determine if MSDE or SQL Express is installed?

Is there a best practice in determining whether MSDE installed on a
workstation or if SQL Express is installed? The SQL Express installs
are all with the default named instance of .\SQLExpress, but it's not
otherwise generally known as to which version is present.
Specifically, a (DOS) bat file is periodically launched to run a sql
script (via osql.exe). Somehow, the bat file needs to handle the
difference between the MSDE default instance and the SQL Express named
instance.
I thought of using the installed paths to make a decision in the bat
file, for instance:
IF EXIST "C:\Program Files\Microsoft SQL Server\90" GOTO :Express
:MSDE
osql.exe -S (local) -E -i myfile.sql -n
GOTO :EOF
:Express
osql.exe -S .\SQLExpress -E -i myfile.sql -n
('Course the second osql.exe reference above could be to sqlcmd.exe
instead).
Thanks!
Hi Mark
SQLPing will give you a list of instances but not the information on
editions see
http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx
You could use SMO, sqlcmd or osql to get the edition information
SERVERPROPERTY ( 'edition')
or
SERVERPROPERTY ( 'Engine Edition' )
but you would need to connect to it to be able to query the server properties.
John
"Mark Lemoine" wrote:

> Is there a best practice in determining whether MSDE installed on a
> workstation or if SQL Express is installed? The SQL Express installs
> are all with the default named instance of .\SQLExpress, but it's not
> otherwise generally known as to which version is present.
> Specifically, a (DOS) bat file is periodically launched to run a sql
> script (via osql.exe). Somehow, the bat file needs to handle the
> difference between the MSDE default instance and the SQL Express named
> instance.
> I thought of using the installed paths to make a decision in the bat
> file, for instance:
> IF EXIST "C:\Program Files\Microsoft SQL Server\90" GOTO :Express
> :MSDE
> osql.exe -S (local) -E -i myfile.sql -n
> GOTO :EOF
> :Express
> osql.exe -S .\SQLExpress -E -i myfile.sql -n
> ('Course the second osql.exe reference above could be to sqlcmd.exe
> instead).
> Thanks!
>

Determine if MSDE or SQL Express is installed?

Is there a best practice in determining whether MSDE installed on a
workstation or if SQL Express is installed? The SQL Express installs
are all with the default named instance of .\SQLExpress, but it's not
otherwise generally known as to which version is present.
Specifically, a (DOS) bat file is periodically launched to run a sql
script (via osql.exe). Somehow, the bat file needs to handle the
difference between the MSDE default instance and the SQL Express named
instance.
I thought of using the installed paths to make a decision in the bat
file, for instance:
IF EXIST "C:\Program Files\Microsoft SQL Server\90" GOTO :Express
:MSDE
osql.exe -S (local) -E -i myfile.sql -n
GOTO :EOF
:Express
osql.exe -S .\SQLExpress -E -i myfile.sql -n
('Course the second osql.exe reference above could be to sqlcmd.exe
instead).
Thanks!Hi Mark
SQLPing will give you a list of instances but not the information on
editions see
http://www.sqlsecurity.com/Tools/FreeTools/tabid/65/Default.aspx
You could use SMO, sqlcmd or osql to get the edition information
SERVERPROPERTY ( 'edition')
or
SERVERPROPERTY ( 'Engine Edition' )
but you would need to connect to it to be able to query the server properties.
John
"Mark Lemoine" wrote:
> Is there a best practice in determining whether MSDE installed on a
> workstation or if SQL Express is installed? The SQL Express installs
> are all with the default named instance of .\SQLExpress, but it's not
> otherwise generally known as to which version is present.
> Specifically, a (DOS) bat file is periodically launched to run a sql
> script (via osql.exe). Somehow, the bat file needs to handle the
> difference between the MSDE default instance and the SQL Express named
> instance.
> I thought of using the installed paths to make a decision in the bat
> file, for instance:
> IF EXIST "C:\Program Files\Microsoft SQL Server\90" GOTO :Express
> :MSDE
> osql.exe -S (local) -E -i myfile.sql -n
> GOTO :EOF
> :Express
> osql.exe -S .\SQLExpress -E -i myfile.sql -n
> ('Course the second osql.exe reference above could be to sqlcmd.exe
> instead).
> Thanks!
>|||SELECT @.@.VERSION
On 5/2/08 5:29 PM, in article 200852172913pozburn@.boulderoutlook.com, "<Paul
Ozburn>" <> wrote:
> Is there also a way to determine whether the server is currently using MSDE or
> SQL2000 (or SQL2005)

Determine Edition in Reporting Services 2000

This may be a simple question, but I need to determine which edition of
Reporting Services I have installed on my SQL Server 2000 server. I have
already confirmed that I am running Enterprise Edition for SQL Server itself,
but cannot find anything that will give me version/edition information for
Reporting Services.
Any help would be greatly appreciated.
Daniel InmanNow I feel stupid. All you need to do is go into Add/Remove programs.
"Daniel Inman" wrote:
> This may be a simple question, but I need to determine which edition of
> Reporting Services I have installed on my SQL Server 2000 server. I have
> already confirmed that I am running Enterprise Edition for SQL Server itself,
> but cannot find anything that will give me version/edition information for
> Reporting Services.
> Any help would be greatly appreciated.
> Daniel Inman
>|||An even simpler alternative is to go to the following url:
http://rsservername/reportserver/
Of course, replace "rsservername" with the real name of your Reporting
Services Server. You'll see the version number at the bottom of that
screen.
Daniel Inman wrote:
> Now I feel stupid. All you need to do is go into Add/Remove programs.
> "Daniel Inman" wrote:
> > This may be a simple question, but I need to determine which edition of
> > Reporting Services I have installed on my SQL Server 2000 server. I have
> > already confirmed that I am running Enterprise Edition for SQL Server itself,
> > but cannot find anything that will give me version/edition information for
> > Reporting Services.
> >
> > Any help would be greatly appreciated.
> >
> > Daniel Inman
> >sql

Detecting SQL Servers on a network

I need to show a list of detected SQL Server 2000 instances installed on a L
AN. I would like to know if anyone knows how to list the servers, similar t
o what Enterprise Manager does with its Server Registration Wizard.
ThanksHi,
From command prompt execute,
ISQL -L
Thanks
Hari
MCDBA
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:983A2E30-10E0-4E3A-BF35-AD0DA6FC7E7A@.microsoft.com...
> I need to show a list of detected SQL Server 2000 instances installed on a
LAN. I would like to know if anyone knows how to list the servers, similar
to what Enterprise Manager does with its Server Registration Wizard.
> Thanks|||Thanks,
Do you have a method that can be done programmatically, rather than from the
command prompt? I need to build this capability into an application for our
developers.
Mike|||SQLDMO
>--Original Message--
>Thanks,
>Do you have a method that can be done programmatically,
rather than from the command prompt? I need to build this
capability into an application for our developers.
>Mike
>.
>|||I believe Enterprise Manager uses the SQLBrowseConnect ODBC function to
enumerate the SQL Servers on a network.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Hi Mike
It would help a great deal if you can supply me with the programming
language that you want this done in.
Regards
Wimpie
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:983A2E30-10E0-4E3A-BF35-AD0DA6FC7E7A@.microsoft.com...
> I need to show a list of detected SQL Server 2000 instances installed on a
LAN. I would like to know if anyone knows how to list the servers, similar
to what Enterprise Manager does with its Server Registration Wizard.
> Thanks|||Me again...
I include the source of one of my VB .Net projects that does this. The is
no need to include any SQL objects in the project since the software
emulates the SQLDMO object in broadcasting a request for identification on
the network.
Hope it helps
Wimpie
----
---
Public Structure ServerInfo
Friend ServerName As String
Friend InstanceName As String
Friend IsClustered As Boolean
Friend Version As String
Friend TCPPort As Long
Friend IPAddress As String
End Structure
Public Sub Start()
Dim objSQLServers() As ServerInfo = EnumSQLServer()
End Sub
Friend Function EnumSQLServer() As ServerInfo()
Dim objUDPClient As New System.Net.Sockets.UdpClient
Dim objRemoteIP As System.Net.IPEndPoint
Dim objAllServers() As ServerInfo
Dim bytData() As Byte = {2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0}
Dim bytReceived() As Byte
Dim strInfo() As String
Dim strHostHeaders() As String
Dim booDone As Boolean = False
Dim i As Long
Dim x As Int16
ReDim strHostHeaders(0)
objUDPClient.Send(bytData, 18, "255.255.255.255", "1434")
While booDone = False
Try
bytReceived = objUDPClient.Receive(objRemoteIP)
Catch
booDone = True
Exit While
End Try
If strHostHeaders(strHostHeaders.Length - 1) <> "" Then
ReDim Preserve strHostHeaders(strHostHeaders.Length)
End If
strHostHeaders(strHostHeaders.Length - 1) =
Mid(System.Text.ASCIIEncoding.ASCII.GetString(bytReceived), 4)
strHostHeaders(strHostHeaders.Length - 1) &= ";IPADDRESS;" &
objRemoteIP.Serialize.Item(4).ToString & "." &
objRemoteIP.Serialize.Item(5).ToString & "." &
objRemoteIP.Serialize.Item(6).ToString & "." &
objRemoteIP.Serialize.Item(7).ToString
If strHostHeaders.Length > 1 Then
If strHostHeaders(strHostHeaders.Length - 1) =
strHostHeaders(strHostHeaders.Length - 2) Then ReDim Preserve
strHostHeaders(strHostHeaders.Length - 2)
End If
End While
objUDPClient.Close()
objUDPClient = Nothing
ReDim objAllServers(strHostHeaders.Length - 1)
For i = 0 To strHostHeaders.Length - 1
strInfo = Split(strHostHeaders(i), ";")
For x = 0 To strInfo.Length - 1
Select Case LCase(strInfo(x))
Case "servername"
objAllServers(i).ServerName = strInfo(x + 1)
Case "instancename"
objAllServers(i).InstanceName = strInfo(x + 1)
Case "isclustered"
objAllServers(i).IsClustered = IIf(LCase(strInfo(x +
1)) = "no", False, True)
Case "version"
objAllServers(i).Version = strInfo(x + 1)
Case "tcp"
objAllServers(i).TCPPort = CLng(strInfo(x + 1))
Case "ipaddress"
objAllServers(i).IPAddress = strInfo(x + 1)
End Select
Next
Next
Return objAllServers
End Function

Detecting local Sql instances

I would like to find out what instances of sql are installed on any given machine. For instance, if a machine has SQL Server 2005, SQL Express 2005 and MSDE 2000 installed. I would like to be able to know the versions of each, and ultimately choose the one which is the best for the user to use.

For example, I would like to rank the instances, 1. SQL Server 2005 2. SQL server 2000, 3. Sql express, 4. MSDE

So I would basically like to default to the best choice available locally for the user.

Is there any way to do this using SMO?

Thanks...

Hi Johnny,

Yes, you could:

DataTable dt;

dt = SmoApplication.EnumAvailableSqlServers("JohnnysServer");

for (int i = 0; i < dt.Rows.Count; i++)
{
MessageBox.Show( dt.Rows["Version"].ToString() );
}

Cheers,
Rob

|||Thanks for your response Robert,

Just a few questions about this...

I have tried running it on a few machines, and on some of them the version was null...do you know why this would happen?

Also, does this specific version differ for the fully blown versions vs the light (sql express/msde) versions? Because I noticed that they can have identical versions....

Thanks again...|||

Hi Johnny,

Yes, the versions will be the same, however the "Edition" property (from memory) will display the actual, well...edition. Have a browse of the datatable colums as there's a heap of properties/columns returned.

Not sure why version would be returned as null, unless of course the service wasn't running or otherwise unavailable.

Cheers,
Rob

Detecting Installed IIS - installing SQL 2005 Standard

I've seen lots of posts but few if any solutions to this apparently common problem.

I'm experiencing a variant - installing SQL 2005 (RTM) on a brand new machine with Server 2003 Standard Ed. SP1, the setup program frequently pauses on steps identified as "Detecting Installed IIS". Setup eventually moves on, but it's taking ages to finish the install.

I've installed this exact version of several identical machines, but this is the first where I've encountered this behavior.

Does anyone have any input on what's really happening here and what to do about it?I guess no one really knows... :)

In my case, I believe that the cause was a DNS issue that caused all name resolution requests to time out. Others have reported issues related to firewalls or antivirus software.|||

Thanks for posting your solution, Carl. What was the DNS issue you were hitting? Did you have to change some settings to get it working? And approximately how long was the slow install? Hours? This issue has appeared a few times on here and I don't think we have a good answer yet other than DNS/firewall/anti-virus issues.

Thanks,
Sam Lester (MSFT)

|||

Now this is stressing the way-back machine!

The slow install was, as I recall, something on the order of 2-5 minutes each time something tried to detect IIS (and it happens several times during the install).

If I recall, the solution was to configure TCP/IP on the install machine to use the local domain controller for DNS rather than my upstream providers' DNS server.

Detecting Installed IIS - installing SQL 2005 Standard

I've seen lots of posts but few if any solutions to this apparently common problem.

I'm experiencing a variant - installing SQL 2005 (RTM) on a brand new machine with Server 2003 Standard Ed. SP1, the setup program frequently pauses on steps identified as "Detecting Installed IIS". Setup eventually moves on, but it's taking ages to finish the install.

I've installed this exact version of several identical machines, but this is the first where I've encountered this behavior.

Does anyone have any input on what's really happening here and what to do about it?I guess no one really knows... :)

In my case, I believe that the cause was a DNS issue that caused all name resolution requests to time out. Others have reported issues related to firewalls or antivirus software.|||

Thanks for posting your solution, Carl. What was the DNS issue you were hitting? Did you have to change some settings to get it working? And approximately how long was the slow install? Hours? This issue has appeared a few times on here and I don't think we have a good answer yet other than DNS/firewall/anti-virus issues.

Thanks,
Sam Lester (MSFT)

|||

Now this is stressing the way-back machine!

The slow install was, as I recall, something on the order of 2-5 minutes each time something tried to detect IIS (and it happens several times during the install).

If I recall, the solution was to configure TCP/IP on the install machine to use the local domain controller for DNS rather than my upstream providers' DNS server.

Detecting Installed IIS - installing SQL 2005 Standard

I've seen lots of posts but few if any solutions to this apparently common problem.

I'm experiencing a variant - installing SQL 2005 (RTM) on a brand new machine with Server 2003 Standard Ed. SP1, the setup program frequently pauses on steps identified as "Detecting Installed IIS". Setup eventually moves on, but it's taking ages to finish the install.

I've installed this exact version of several identical machines, but this is the first where I've encountered this behavior.

Does anyone have any input on what's really happening here and what to do about it?I guess no one really knows... :)

In my case, I believe that the cause was a DNS issue that caused all name resolution requests to time out. Others have reported issues related to firewalls or antivirus software.|||

Thanks for posting your solution, Carl. What was the DNS issue you were hitting? Did you have to change some settings to get it working? And approximately how long was the slow install? Hours? This issue has appeared a few times on here and I don't think we have a good answer yet other than DNS/firewall/anti-virus issues.

Thanks,
Sam Lester (MSFT)

|||

Now this is stressing the way-back machine!

The slow install was, as I recall, something on the order of 2-5 minutes each time something tried to detect IIS (and it happens several times during the install).

If I recall, the solution was to configure TCP/IP on the install machine to use the local domain controller for DNS rather than my upstream providers' DNS server.

sql

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.

Detecting Custom Objects Used by SQL Server 2000 objects

Hello,
I work as a software engineer and we have installed third party and custom
in-house dlls and ocx on our SQL Server 2000 server to support our business
applications. These dlls and ocx are referenced by the database
objects(jobs, storedprocedures). What I need to do is to generate a list of
all the dlls and ocx that our SQL Server reference, so that I can copy these
files out to our new future SQL Server box.
Does anyone here know how to do this? Is there a system table in one of the
system databases that keep track of the information I'm seeking?
Thanks you.
Scott Yu
"Scott Yu" <ScottYu@.discussions.microsoft.com> wrote in message
news:C95F6558-D80C-44F7-8E2D-65ED12C13721@.microsoft.com...
> Hello,
> I work as a software engineer and we have installed third party and custom
> in-house dlls and ocx on our SQL Server 2000 server to support our
> business
> applications. These dlls and ocx are referenced by the database
> objects(jobs, storedprocedures). What I need to do is to generate a list
> of
> all the dlls and ocx that our SQL Server reference, so that I can copy
> these
> files out to our new future SQL Server box.
> Does anyone here know how to do this? Is there a system table in one of
> the
> system databases that keep track of the information I'm seeking?
>
Unfortunately, you will have to dig through the text of the stored
procedures for calls to sp_oacreate.
set textsize 64000
exec sp_msforeachdb '
select text from syscomments
where text like ''%sp_oacreate%'''
This will give you the progid's of the com components used by sql server.
They must be copied to the new server and registered there, along with all
of their dependencies.
This is an exceedingly difficult thing for a DBA to get right. You may need
to track down the owners of each component to sucessfully move it to the new
server.
David
|||Hey David,
Thanks for the script. I pretty much did the same thing by scripting out
the storedprocedures and jobs, but that was before I learned of
sp_msforeachdb, thanks to you. The hardest part is trying to locate all the
dependent dlls. Another dll hell.
Thank you David.
Scott Yu
"David Browne" wrote:

> "Scott Yu" <ScottYu@.discussions.microsoft.com> wrote in message
> news:C95F6558-D80C-44F7-8E2D-65ED12C13721@.microsoft.com...
> Unfortunately, you will have to dig through the text of the stored
> procedures for calls to sp_oacreate.
> set textsize 64000
> exec sp_msforeachdb '
> select text from syscomments
> where text like ''%sp_oacreate%'''
> This will give you the progid's of the com components used by sql server.
> They must be copied to the new server and registered there, along with all
> of their dependencies.
> This is an exceedingly difficult thing for a DBA to get right. You may need
> to track down the owners of each component to sucessfully move it to the new
> server.
> David
>
>
|||One more thing to remember when you are searching using the LIKE operation:
"_" is a wildcard character meaning "any single character." When you want
the literal "_", you'll want to use brackets like so:
SELECT [name]
FROM syscomments
WHERE [text] LIKE '%sp[_]oacreate%"
Sincerely,
Anthony Thomas
"Scott Yu" wrote:
[vbcol=seagreen]
> Hey David,
> Thanks for the script. I pretty much did the same thing by scripting out
> the storedprocedures and jobs, but that was before I learned of
> sp_msforeachdb, thanks to you. The hardest part is trying to locate all the
> dependent dlls. Another dll hell.
> Thank you David.
> Scott Yu
> "David Browne" wrote:
|||Thank you very much Anthony. What is the difference between "%" and "_" in
TL SQL?
Scott
"AnthonyThomas" wrote:
[vbcol=seagreen]
> One more thing to remember when you are searching using the LIKE operation:
> "_" is a wildcard character meaning "any single character." When you want
> the literal "_", you'll want to use brackets like so:
> SELECT [name]
> FROM syscomments
> WHERE [text] LIKE '%sp[_]oacreate%"
> Sincerely,
>
> Anthony Thomas
>
> "Scott Yu" wrote:
|||Never mind. After re-reading your reply, I understoodd the difference
between "%" and "_".
Thank you.
"AnthonyThomas" wrote:
[vbcol=seagreen]
> One more thing to remember when you are searching using the LIKE operation:
> "_" is a wildcard character meaning "any single character." When you want
> the literal "_", you'll want to use brackets like so:
> SELECT [name]
> FROM syscomments
> WHERE [text] LIKE '%sp[_]oacreate%"
> Sincerely,
>
> Anthony Thomas
>
> "Scott Yu" wrote:
sql

Detecting Custom Objects Used by SQL Server 2000 objects

Hello,
I work as a software engineer and we have installed third party and custom
in-house dlls and ocx on our SQL Server 2000 server to support our business
applications. These dlls and ocx are referenced by the database
objects(jobs, storedprocedures). What I need to do is to generate a list of
all the dlls and ocx that our SQL Server reference, so that I can copy these
files out to our new future SQL Server box.
Does anyone here know how to do this? Is there a system table in one of the
system databases that keep track of the information I'm seeking?
Thanks you.
Scott Yu"Scott Yu" <ScottYu@.discussions.microsoft.com> wrote in message
news:C95F6558-D80C-44F7-8E2D-65ED12C13721@.microsoft.com...
> Hello,
> I work as a software engineer and we have installed third party and custom
> in-house dlls and ocx on our SQL Server 2000 server to support our
> business
> applications. These dlls and ocx are referenced by the database
> objects(jobs, storedprocedures). What I need to do is to generate a list
> of
> all the dlls and ocx that our SQL Server reference, so that I can copy
> these
> files out to our new future SQL Server box.
> Does anyone here know how to do this? Is there a system table in one of
> the
> system databases that keep track of the information I'm seeking?
>
Unfortunately, you will have to dig through the text of the stored
procedures for calls to sp_oacreate.
set textsize 64000
exec sp_msforeachdb '
select text from syscomments
where text like ''%sp_oacreate%'''
This will give you the progid's of the com components used by sql server.
They must be copied to the new server and registered there, along with all
of their dependencies.
This is an exceedingly difficult thing for a DBA to get right. You may need
to track down the owners of each component to sucessfully move it to the new
server.
David|||Hey David,
Thanks for the script. I pretty much did the same thing by scripting out
the storedprocedures and jobs, but that was before I learned of
sp_msforeachdb, thanks to you. The hardest part is trying to locate all th
e
dependent dlls. Another dll hell.
Thank you David.
Scott Yu
"David Browne" wrote:

> "Scott Yu" <ScottYu@.discussions.microsoft.com> wrote in message
> news:C95F6558-D80C-44F7-8E2D-65ED12C13721@.microsoft.com...
> Unfortunately, you will have to dig through the text of the stored
> procedures for calls to sp_oacreate.
> set textsize 64000
> exec sp_msforeachdb '
> select text from syscomments
> where text like ''%sp_oacreate%'''
> This will give you the progid's of the com components used by sql server.
> They must be copied to the new server and registered there, along with all
> of their dependencies.
> This is an exceedingly difficult thing for a DBA to get right. You may ne
ed
> to track down the owners of each component to sucessfully move it to the n
ew
> server.
> David
>
>|||One more thing to remember when you are searching using the LIKE operation:
"_" is a wildcard character meaning "any single character." When you want
the literal "_", you'll want to use brackets like so:
SELECT [name]
FROM syscomments
WHERE [text] LIKE '%sp[_]oacreate%"
Sincerely,
Anthony Thomas
"Scott Yu" wrote:
[vbcol=seagreen]
> Hey David,
> Thanks for the script. I pretty much did the same thing by scripting out
> the storedprocedures and jobs, but that was before I learned of
> sp_msforeachdb, thanks to you. The hardest part is trying to locate all
the
> dependent dlls. Another dll hell.
> Thank you David.
> Scott Yu
> "David Browne" wrote:
>|||Thank you very much Anthony. What is the difference between "%" and "_" in
TL SQL?
Scott
"AnthonyThomas" wrote:
[vbcol=seagreen]
> One more thing to remember when you are searching using the LIKE operation
:
> "_" is a wildcard character meaning "any single character." When you want
> the literal "_", you'll want to use brackets like so:
> SELECT [name]
> FROM syscomments
> WHERE [text] LIKE '%sp[_]oacreate%"
> Sincerely,
>
> Anthony Thomas
>
> "Scott Yu" wrote:
>|||Never mind. After re-reading your reply, I understoodd the difference
between "%" and "_".
Thank you.
"AnthonyThomas" wrote:
[vbcol=seagreen]
> One more thing to remember when you are searching using the LIKE operation
:
> "_" is a wildcard character meaning "any single character." When you want
> the literal "_", you'll want to use brackets like so:
> SELECT [name]
> FROM syscomments
> WHERE [text] LIKE '%sp[_]oacreate%"
> Sincerely,
>
> Anthony Thomas
>
> "Scott Yu" wrote:
>

Detecting Custom Objects Used by SQL Server 2000 objects

Hello,
I work as a software engineer and we have installed third party and custom
in-house dlls and ocx on our SQL Server 2000 server to support our business
applications. These dlls and ocx are referenced by the database
objects(jobs, storedprocedures). What I need to do is to generate a list of
all the dlls and ocx that our SQL Server reference, so that I can copy these
files out to our new future SQL Server box.
Does anyone here know how to do this? Is there a system table in one of the
system databases that keep track of the information I'm seeking?
Thanks you.
Scott Yu"Scott Yu" <ScottYu@.discussions.microsoft.com> wrote in message
news:C95F6558-D80C-44F7-8E2D-65ED12C13721@.microsoft.com...
> Hello,
> I work as a software engineer and we have installed third party and custom
> in-house dlls and ocx on our SQL Server 2000 server to support our
> business
> applications. These dlls and ocx are referenced by the database
> objects(jobs, storedprocedures). What I need to do is to generate a list
> of
> all the dlls and ocx that our SQL Server reference, so that I can copy
> these
> files out to our new future SQL Server box.
> Does anyone here know how to do this? Is there a system table in one of
> the
> system databases that keep track of the information I'm seeking?
>
Unfortunately, you will have to dig through the text of the stored
procedures for calls to sp_oacreate.
set textsize 64000
exec sp_msforeachdb '
select text from syscomments
where text like ''%sp_oacreate%'''
This will give you the progid's of the com components used by sql server.
They must be copied to the new server and registered there, along with all
of their dependencies.
This is an exceedingly difficult thing for a DBA to get right. You may need
to track down the owners of each component to sucessfully move it to the new
server.
David|||Hey David,
Thanks for the script. I pretty much did the same thing by scripting out
the storedprocedures and jobs, but that was before I learned of
sp_msforeachdb, thanks to you. The hardest part is trying to locate all the
dependent dlls. Another dll hell.
Thank you David.
Scott Yu
"David Browne" wrote:
> "Scott Yu" <ScottYu@.discussions.microsoft.com> wrote in message
> news:C95F6558-D80C-44F7-8E2D-65ED12C13721@.microsoft.com...
> > Hello,
> >
> > I work as a software engineer and we have installed third party and custom
> > in-house dlls and ocx on our SQL Server 2000 server to support our
> > business
> > applications. These dlls and ocx are referenced by the database
> > objects(jobs, storedprocedures). What I need to do is to generate a list
> > of
> > all the dlls and ocx that our SQL Server reference, so that I can copy
> > these
> > files out to our new future SQL Server box.
> >
> > Does anyone here know how to do this? Is there a system table in one of
> > the
> > system databases that keep track of the information I'm seeking?
> >
> Unfortunately, you will have to dig through the text of the stored
> procedures for calls to sp_oacreate.
> set textsize 64000
> exec sp_msforeachdb '
> select text from syscomments
> where text like ''%sp_oacreate%'''
> This will give you the progid's of the com components used by sql server.
> They must be copied to the new server and registered there, along with all
> of their dependencies.
> This is an exceedingly difficult thing for a DBA to get right. You may need
> to track down the owners of each component to sucessfully move it to the new
> server.
> David
>
>|||One more thing to remember when you are searching using the LIKE operation:
"_" is a wildcard character meaning "any single character." When you want
the literal "_", you'll want to use brackets like so:
SELECT [name]
FROM syscomments
WHERE [text] LIKE '%sp[_]oacreate%"
Sincerely,
Anthony Thomas
"Scott Yu" wrote:
> Hey David,
> Thanks for the script. I pretty much did the same thing by scripting out
> the storedprocedures and jobs, but that was before I learned of
> sp_msforeachdb, thanks to you. The hardest part is trying to locate all the
> dependent dlls. Another dll hell.
> Thank you David.
> Scott Yu
> "David Browne" wrote:
> >
> > "Scott Yu" <ScottYu@.discussions.microsoft.com> wrote in message
> > news:C95F6558-D80C-44F7-8E2D-65ED12C13721@.microsoft.com...
> > > Hello,
> > >
> > > I work as a software engineer and we have installed third party and custom
> > > in-house dlls and ocx on our SQL Server 2000 server to support our
> > > business
> > > applications. These dlls and ocx are referenced by the database
> > > objects(jobs, storedprocedures). What I need to do is to generate a list
> > > of
> > > all the dlls and ocx that our SQL Server reference, so that I can copy
> > > these
> > > files out to our new future SQL Server box.
> > >
> > > Does anyone here know how to do this? Is there a system table in one of
> > > the
> > > system databases that keep track of the information I'm seeking?
> > >
> >
> > Unfortunately, you will have to dig through the text of the stored
> > procedures for calls to sp_oacreate.
> >
> > set textsize 64000
> > exec sp_msforeachdb '
> > select text from syscomments
> > where text like ''%sp_oacreate%'''
> >
> > This will give you the progid's of the com components used by sql server.
> > They must be copied to the new server and registered there, along with all
> > of their dependencies.
> >
> > This is an exceedingly difficult thing for a DBA to get right. You may need
> > to track down the owners of each component to sucessfully move it to the new
> > server.
> >
> > David
> >
> >
> >|||Thank you very much Anthony. What is the difference between "%" and "_" in
TL SQL?
Scott
"AnthonyThomas" wrote:
> One more thing to remember when you are searching using the LIKE operation:
> "_" is a wildcard character meaning "any single character." When you want
> the literal "_", you'll want to use brackets like so:
> SELECT [name]
> FROM syscomments
> WHERE [text] LIKE '%sp[_]oacreate%"
> Sincerely,
>
> Anthony Thomas
>
> "Scott Yu" wrote:
> > Hey David,
> >
> > Thanks for the script. I pretty much did the same thing by scripting out
> > the storedprocedures and jobs, but that was before I learned of
> > sp_msforeachdb, thanks to you. The hardest part is trying to locate all the
> > dependent dlls. Another dll hell.
> >
> > Thank you David.
> >
> > Scott Yu
> >
> > "David Browne" wrote:
> >
> > >
> > > "Scott Yu" <ScottYu@.discussions.microsoft.com> wrote in message
> > > news:C95F6558-D80C-44F7-8E2D-65ED12C13721@.microsoft.com...
> > > > Hello,
> > > >
> > > > I work as a software engineer and we have installed third party and custom
> > > > in-house dlls and ocx on our SQL Server 2000 server to support our
> > > > business
> > > > applications. These dlls and ocx are referenced by the database
> > > > objects(jobs, storedprocedures). What I need to do is to generate a list
> > > > of
> > > > all the dlls and ocx that our SQL Server reference, so that I can copy
> > > > these
> > > > files out to our new future SQL Server box.
> > > >
> > > > Does anyone here know how to do this? Is there a system table in one of
> > > > the
> > > > system databases that keep track of the information I'm seeking?
> > > >
> > >
> > > Unfortunately, you will have to dig through the text of the stored
> > > procedures for calls to sp_oacreate.
> > >
> > > set textsize 64000
> > > exec sp_msforeachdb '
> > > select text from syscomments
> > > where text like ''%sp_oacreate%'''
> > >
> > > This will give you the progid's of the com components used by sql server.
> > > They must be copied to the new server and registered there, along with all
> > > of their dependencies.
> > >
> > > This is an exceedingly difficult thing for a DBA to get right. You may need
> > > to track down the owners of each component to sucessfully move it to the new
> > > server.
> > >
> > > David
> > >
> > >
> > >|||Never mind. After re-reading your reply, I understoodd the difference
between "%" and "_".
Thank you.
"AnthonyThomas" wrote:
> One more thing to remember when you are searching using the LIKE operation:
> "_" is a wildcard character meaning "any single character." When you want
> the literal "_", you'll want to use brackets like so:
> SELECT [name]
> FROM syscomments
> WHERE [text] LIKE '%sp[_]oacreate%"
> Sincerely,
>
> Anthony Thomas
>
> "Scott Yu" wrote:
> > Hey David,
> >
> > Thanks for the script. I pretty much did the same thing by scripting out
> > the storedprocedures and jobs, but that was before I learned of
> > sp_msforeachdb, thanks to you. The hardest part is trying to locate all the
> > dependent dlls. Another dll hell.
> >
> > Thank you David.
> >
> > Scott Yu
> >
> > "David Browne" wrote:
> >
> > >
> > > "Scott Yu" <ScottYu@.discussions.microsoft.com> wrote in message
> > > news:C95F6558-D80C-44F7-8E2D-65ED12C13721@.microsoft.com...
> > > > Hello,
> > > >
> > > > I work as a software engineer and we have installed third party and custom
> > > > in-house dlls and ocx on our SQL Server 2000 server to support our
> > > > business
> > > > applications. These dlls and ocx are referenced by the database
> > > > objects(jobs, storedprocedures). What I need to do is to generate a list
> > > > of
> > > > all the dlls and ocx that our SQL Server reference, so that I can copy
> > > > these
> > > > files out to our new future SQL Server box.
> > > >
> > > > Does anyone here know how to do this? Is there a system table in one of
> > > > the
> > > > system databases that keep track of the information I'm seeking?
> > > >
> > >
> > > Unfortunately, you will have to dig through the text of the stored
> > > procedures for calls to sp_oacreate.
> > >
> > > set textsize 64000
> > > exec sp_msforeachdb '
> > > select text from syscomments
> > > where text like ''%sp_oacreate%'''
> > >
> > > This will give you the progid's of the com components used by sql server.
> > > They must be copied to the new server and registered there, along with all
> > > of their dependencies.
> > >
> > > This is an exceedingly difficult thing for a DBA to get right. You may need
> > > to track down the owners of each component to sucessfully move it to the new
> > > server.
> > >
> > > David
> > >
> > >
> > >

Detect Licensing

Hello

I am trying to find out if versions of SQL SERVER 2005 we have installed have full or Developer Licenses.

They were installed previously by someone who no longer works here, and we do not the versions on record.

We have enough full licenses, so we just want to make sure the correct ones are set up on our servers.

Anyone know how/where we can find this information?

I found the answer - SELECT @.@.version

Thanks