MSSQL.1, .2, .3....?

For some reason Sql 2005, by default, creates different folder paths (such as MSSQL.1, MSSQL,2, etc) for different services.

1. Is there a utiltiy that can tell me what service is stored in what folder?

2. I noticed that Integraiton Servcies does not seem to have a seperate ("MSSQL.x") folder. Why?

Any help much appreciated,

Barkingdog

"Is there a utiltiy that can tell me what service is stored in what folder?"

Yes, SQL Server Configuration Manager. Select SQL Server 2005 Services after you start the tool. Right-click on a particular service and select properties. Select the Service tab and the path is in the Binary Path attribute.

" I noticed that Integraiton Servcies does not seem to have a seperate ("MSSQL.x") folder. Why?"

My guess is that the sql directory structure is this way because SSIS does not require several other OS files as do the other services. But thats a guess. It is what it is :)

HTH,

Derek

MSSQL.1 directory

Hi,
I just did a fresh install of SQL 2005, default instance, to a new server. I
specified the root of D:\ as the target for the install, however I ended up
with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
MSSQL.1 the norm in 2k5?
Thanks in advance.
That's the norm with 2005. I think they like seeing their name in print. I
don't know the intention of MSSQL.1.
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
> Hi,
> I just did a fresh install of SQL 2005, default instance, to a new server.
I
> specified the root of D:\ as the target for the install, however I ended
up
> with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
> MSSQL.1 the norm in 2k5?
> Thanks in advance.
|||New naming convention. Install another SQL component (Analysis services,
Reporting Services) and you will see a MSSQL.2 folder. Upgrades and service
packs will also create new folders for newer versions, at least for the
binaries. It certainly makes rollbacks easier.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
> Hi,
> I just did a fresh install of SQL 2005, default instance, to a new server.
> I
> specified the root of D:\ as the target for the install, however I ended
> up
> with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
> MSSQL.1 the norm in 2k5?
> Thanks in advance.
|||Cool, thank you both.
"Geoff N. Hiten" wrote:

> New naming convention. Install another SQL component (Analysis services,
> Reporting Services) and you will see a MSSQL.2 folder. Upgrades and service
> packs will also create new folders for newer versions, at least for the
> binaries. It certainly makes rollbacks easier.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
> news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
>
>
|||if you want to know what MSSQL.1 corresponds to you can go into :
HKLM\SOFTWARE\MICROSOFT\MICROSOFT SQL SERVER\INSTANCE NAMES\SQL

MSSQL.1 directory

Hi,
I just did a fresh install of SQL 2005, default instance, to a new server. I
specified the root of D:\ as the target for the install, however I ended up
with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
MSSQL.1 the norm in 2k5?
Thanks in advance.That's the norm with 2005. I think they like seeing their name in print. I
don't know the intention of MSSQL.1.
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
> Hi,
> I just did a fresh install of SQL 2005, default instance, to a new server.
I
> specified the root of D:\ as the target for the install, however I ended
up
> with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
> MSSQL.1 the norm in 2k5?
> Thanks in advance.|||New naming convention. Install another SQL component (Analysis services,
Reporting Services) and you will see a MSSQL.2 folder. Upgrades and service
packs will also create new folders for newer versions, at least for the
binaries. It certainly makes rollbacks easier.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
> Hi,
> I just did a fresh install of SQL 2005, default instance, to a new server.
> I
> specified the root of D:\ as the target for the install, however I ended
> up
> with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
> MSSQL.1 the norm in 2k5?
> Thanks in advance.|||Cool, thank you both.
"Geoff N. Hiten" wrote:

> New naming convention. Install another SQL component (Analysis services,
> Reporting Services) and you will see a MSSQL.2 folder. Upgrades and servi
ce
> packs will also create new folders for newer versions, at least for the
> binaries. It certainly makes rollbacks easier.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
> news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
>
>|||if you want to know what MSSQL.1 corresponds to you can go into :
HKLM\SOFTWARE\MICROSOFT\MICROSOFT SQL SERVER\INSTANCE NAMES\SQL

MSSQL.1 directory

Hi,
I just did a fresh install of SQL 2005, default instance, to a new server. I
specified the root of D:\ as the target for the install, however I ended up
with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
MSSQL.1 the norm in 2k5?
Thanks in advance.That's the norm with 2005. I think they like seeing their name in print. I
don't know the intention of MSSQL.1.
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
> Hi,
> I just did a fresh install of SQL 2005, default instance, to a new server.
I
> specified the root of D:\ as the target for the install, however I ended
up
> with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
> MSSQL.1 the norm in 2k5?
> Thanks in advance.|||New naming convention. Install another SQL component (Analysis services,
Reporting Services) and you will see a MSSQL.2 folder. Upgrades and service
packs will also create new folders for newer versions, at least for the
binaries. It certainly makes rollbacks easier.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
> Hi,
> I just did a fresh install of SQL 2005, default instance, to a new server.
> I
> specified the root of D:\ as the target for the install, however I ended
> up
> with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
> MSSQL.1 the norm in 2k5?
> Thanks in advance.|||Cool, thank you both.
"Geoff N. Hiten" wrote:
> New naming convention. Install another SQL component (Analysis services,
> Reporting Services) and you will see a MSSQL.2 folder. Upgrades and service
> packs will also create new folders for newer versions, at least for the
> binaries. It certainly makes rollbacks easier.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "sqlboy2000" <sqlboy2000@.discussions.microsoft.com> wrote in message
> news:A30BA7DB-EB9B-45F2-B37D-E1949D0FE0B4@.microsoft.com...
> > Hi,
> > I just did a fresh install of SQL 2005, default instance, to a new server.
> > I
> > specified the root of D:\ as the target for the install, however I ended
> > up
> > with D:\MSSQL.1\MSSQL as my physical directory. Did I miss something or is
> > MSSQL.1 the norm in 2k5?
> >
> > Thanks in advance.
>
>|||if you want to know what MSSQL.1 corresponds to you can go into :
HKLM\SOFTWARE\MICROSOFT\MICROSOFT SQL SERVER\INSTANCE NAMES\SQL