How to determine if SQL 7 SP4 or higher is installed using Registry

I am developing an .msi package that requires SQL 7 SP4 or higher to be installed. I would like to use the registry to confirm a valid SQL installation and from there I can determine if my .msi installation should continue as normal or display an error m
essage asking to install SQL first.
I couldn't find much solid information on the web. This is all I have:
All versions:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQLServer
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
6.0 and above:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\MSDTC
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLExecutive
7.0 and above:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLServerAgent
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server 7
HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServ65
However, what key and value should I use to look for the specific SQL version? Does this value hold a simple number like '7' and for any more recent versions of SQL would this number be higher in value? Such as '2000' for a SQL 2000 unit?
Thanks for your time
HKEY_LOCAL_MACHINE/Software/Microsoft/MSSQLServer/MSSQLServer/CurrentVersion
/CSDVersion
Rohtash Kapoor
http://www.sqlmantra.com
"k8e" <anonymous@.discussions.microsoft.com> wrote in message
news:0E857F02-C889-4951-BC38-1ADFB361B9EA@.microsoft.com...
> I am developing an .msi package that requires SQL 7 SP4 or higher to be
installed. I would like to use the registry to confirm a valid SQL
installation and from there I can determine if my .msi installation should
continue as normal or display an error message asking to install SQL first.
> --
> I couldn't find much solid information on the web. This is all I have:
> All versions:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQLServer
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
> 6.0 and above:
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\MSDTC
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLExecutive
> 7.0 and above:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLServerAgent
> HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server 7
> HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServ65
> --
> However, what key and value should I use to look for the specific SQL
version? Does this value hold a simple number like '7' and for any more
recent versions of SQL would this number be higher in value? Such as '2000'
for a SQL 2000 unit?
> Thanks for your time

How to Deploy Reports to a Production Environment

Our situation is that we are developing a set of "master" reports locally
using Visual Studio .NET 2003 (and, of course, the Reporting Services
designer). Once the master reports are finished, we will need to install
these reports to our customers' computers (their computers are not a part of
our network, we don't have access to them to deploy from our computers and
the Visual Studio .NET 2003 solution/project). And then we will need to
deploy to the ReportServer on their server.
Additionally, the customers' server will have VB .NET installed (the basic
edition to allow RDL development).
So, should we simply copy the solution, project, RDS, and RDL files to the
customers' server, then open the solution in VB .NET, and deploy? Or is
there a better way?
Also, since we are developing the master reports in a solution/project in
Visual Studio .NET on our local development servers, is there any
compatibility issues in trying to open that same solution in VB .NET on the
customers' server?
Thanks.I would think the easiest way would be to build a quick app to do this using
the CreateReport SOAP Api. You could then make this app as simple or
complex as you need it and not need to worry about your customers having any
VS components. We shipped a sample app (RSExplorer I believe) that does
allow you to deploy but it would have to be modified if you wanted to easily
upload a directory of rdls.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Belak" <nospam@.nospam.com> wrote in message
news:OrhITzzmEHA.3264@.TK2MSFTNGP12.phx.gbl...
> Our situation is that we are developing a set of "master" reports locally
> using Visual Studio .NET 2003 (and, of course, the Reporting Services
> designer). Once the master reports are finished, we will need to install
> these reports to our customers' computers (their computers are not a part
of
> our network, we don't have access to them to deploy from our computers and
> the Visual Studio .NET 2003 solution/project). And then we will need to
> deploy to the ReportServer on their server.
> Additionally, the customers' server will have VB .NET installed (the basic
> edition to allow RDL development).
> So, should we simply copy the solution, project, RDS, and RDL files to the
> customers' server, then open the solution in VB .NET, and deploy? Or is
> there a better way?
> Also, since we are developing the master reports in a solution/project in
> Visual Studio .NET on our local development servers, is there any
> compatibility issues in trying to open that same solution in VB .NET on
the
> customers' server?
> Thanks.
>

How to deploy assembly from remote system, without using VS.NET

Hi

I'm developing a tool to deploy the CLR objects from any where to the server

But I'm unable to deploy from remote system to the server.

I'm getting the error like

CREATE ASSEMBLY failed because it could not open the physical file 'D:\Working\DBS2005V2\GL\GLREPORTS\DBS.GL.RM.SQL\bin\Debug\sample.dll': 3(The system cannot find the path specified.).

when I try to deploy using

EXEC dbo.sp_executesql @.statement = N' CREATE ASSEMBLY [DBS.GL.RM.SQL]

FROM ''D:\Working\DBS2005V2\GL\GLREPORTS\DBS.GL.RM.SQL\bin\Debug\sample.dll''

WITH PERMISSION_SET = SAFE'

can anybody tell how to generate assembly_bits for assembly

the VS.NEt is generating assembly bits instead of physical path to deploy the assembly on the remote server.

as

CREATE ASSEMBLY [sample]

AUTHORIZATION [dbo]

FROM 0x4D5A90000300000004000000FFFF0000B800000000000000400000000000000000000000000000000000000000000000000000000000000000000000800000000E1FBA0E00B409CD21B8014CCD215 ..

WITH PERMISSION_SET = SAFE

But nothing is provided reg this in MSDN.

will u help me in handle this please

Thank u

See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=288119&SiteID=1 for code that will allow you to generate the assembly bits string.