Adding a custom named instance to Windows Firewall exception list

We install SQL Express 2005 with a custom named instance. Since a named instance uses dynamic ports, how can I add this named instance to the Windows Firewall exception list? Previously with MSDE 2000 we installed as default, then I added port 1433 to the Firewall exception list.

Is there a way to install SQL Express to a static port (programmatically)? Or, is there a better method, like adding the SQL custom named instance service to the firewall exception list?

You can add a firewall exception for the specific executable rather than the port number. Details are available in this KB Article,

Mike

Adding a custom named instance to Windows Firewall exception list

We install SQL Express 2005 with a custom named instance. Since a named instance uses dynamic ports, how can I add this named instance to the Windows Firewall exception list? Previously with MSDE 2000 we installed as default, then I added port 1433 to the Firewall exception list.

Is there a way to install SQL Express to a static port (programmatically)? Or, is there a better method, like adding the SQL custom named instance service to the firewall exception list?

You can add a firewall exception for the specific executable rather than the port number. Details are available in this KB Article,

Mike

sql

Adding 2nd instance of SQL

I am adding a 2nd instance of SQL on a SQL SP4 box. Can someone please
clarify a few things for me?
1. Can this be done during productions hours - does it requre a reboot?
2. Does it actually install another full version of SQL - I only have a CD
that has SQL 2000 on it so I would have to apply the SP 4 after the fact -
will this affect the production instance default instance)
3. Does it use a different service account to start?
4. Can it use a second bound IP address?
Any other tips I should be aware of? Thanks for your time.
Hi
"Bad Beagle" wrote:

> I am adding a 2nd instance of SQL on a SQL SP4 box. Can someone please
> clarify a few things for me?
> 1. Can this be done during productions hours - does it requre a reboot?
It should not require a re-boot, but it would not be a good idea to do it on
a production server whilst it is being used.

> 2. Does it actually install another full version of SQL - I only have a CD
> that has SQL 2000 on it so I would have to apply the SP 4 after the fact -
> will this affect the production instance default instance)
Yes you would need to apply a service pack separately.

> 3. Does it use a different service account to start?
This is however you configure it, the can be the same if required.

> 4. Can it use a second bound IP address?
You could do this via a firewall and filter on tcp/ip ports or possibly by
using the TCP/IP filtering in the advanced options of the network connection.
> Any other tips I should be aware of? Thanks for your time.
>
>
Having a second instance will use resources on this machine, you should not
(really) have a second instance on a production server if you can avoid it,
and certainly test/development instances should be kept separate.
John
|||Hello,
Thank you for posting. Also, thanks very much to John for his contribution.
It seems that John has essentially answered all the questions appropriately.
You can install the instance without re-booting the system. Application of
SP4 does require a reboot. I would also recommend that, regardless, you do
reboot the system simply to refresh services and what not. You can
install the instance followed by SP4 then reboot.
My understanding is that the root of this question is "Can you do the
installation on a production server while it is being used?" While it
should work without issue, there are a number of reasons not to attempt
this. First, if something does go wrong, you may unexpectedly bring down
your production server while people are using it, thus potentially losing
data and incurring user and executive wrath: something we all generally
want to avoid. Secondly, and particularly with SP updates, installations
have been known to fail silently and return a successful message without
properly updating services. It's very much recommended to do any such type
of major administration while the database is not being accessed.
You can configure the service account either during the installation of the
SQL Server, or you can update it later through SQL Enterprise manager. As
John mentioned, you can set it to a different account or the same account
depending on your requirements.
You can bind each instance that you install to a separate port, but you can
not specify an IP address for each instance. Instead, the port for the
TCP/IP network protocal is dynamically configured during installation. As
John suggests you can manage this using NAT at your Router/Firewall. To
check/change the port for the instance, you can open SQL Enterprise Manger,
Right click the instance you want to change, select Properties > Network
Configuration... > TCP/IP > Properties...
John also brings up a very good point about the performance implications of
running an extra instance on a production server. Basically, when you add
an instance, all the following are replicated, taking up additional
resources:

> SQL Server database engine
> System and user databases.
> The SQL Server and SQL Server Agent services.
> The registry keys associated with the database engine and the SQL Server
and SQL Server Agent services.
> Network connection addresses
(*see:
http://msdn.microsoft.com/library/de...us/architec/8_
ar_cs_9i5u.asp)
Please also review the BOL section on 'multiple instance of SQL Server' in
the index for BOL. See particularly the sections "best practices', 'memory
usage', and 'when to use' to better determine if installing separate
instances is actually in your best interest.
Hope this helps!
Sincerely,
Dana Brash [MSFT]
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "Bad Beagle" <maxwelli@.nospam.postalias>
>Subject: Adding 2nd instance of SQL
>Date: Fri, 13 Jan 2006 07:29:45 -0700
>Lines: 12
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <eScgO3EGGHA.3944@.tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 199.213.91.1
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msft ngp13.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:417520
>X-Tomcat-NG: microsoft.public.sqlserver.server
>I am adding a 2nd instance of SQL on a SQL SP4 box. Can someone please
>clarify a few things for me?
>1. Can this be done during productions hours - does it requre a reboot?
>2. Does it actually install another full version of SQL - I only have a
CD
>that has SQL 2000 on it so I would have to apply the SP 4 after the fact -
>will this affect the production instance default instance)
>3. Does it use a different service account to start?
>4. Can it use a second bound IP address?
>Any other tips I should be aware of? Thanks for your time.
>
>
|||Hi,
Just want to say Hi, and I was wondering how everything is going. If
anything is unclear, please let me know. It is my pleasure to be of
assistance.
Hope this helps!
Sincerely,
Dana Brash
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "Bad Beagle" <maxwelli@.nospam.postalias>
>Subject: Adding 2nd instance of SQL
>Date: Fri, 13 Jan 2006 07:29:45 -0700
>Lines: 12
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <eScgO3EGGHA.3944@.tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 199.213.91.1
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msft ngp13.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:417520
>X-Tomcat-NG: microsoft.public.sqlserver.server
>I am adding a 2nd instance of SQL on a SQL SP4 box. Can someone please
>clarify a few things for me?
>1. Can this be done during productions hours - does it requre a reboot?
>2. Does it actually install another full version of SQL - I only have a
CD
>that has SQL 2000 on it so I would have to apply the SP 4 after the fact -
>will this affect the production instance default instance)
>3. Does it use a different service account to start?
>4. Can it use a second bound IP address?
>Any other tips I should be aware of? Thanks for your time.
>
>
|||Hi,
Just a followup on this post. I am wondering if you have any questions or
concerns about this issue. If you need further assistance, please do not
hesitate to let me know.
Hope this helps!
Sincerely,
Dana Brash
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "Bad Beagle" <maxwelli@.nospam.postalias>
>Subject: Adding 2nd instance of SQL
>Date: Fri, 13 Jan 2006 07:29:45 -0700
>Lines: 12
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <eScgO3EGGHA.3944@.tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 199.213.91.1
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msft ngp13.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:417520
>X-Tomcat-NG: microsoft.public.sqlserver.server
>I am adding a 2nd instance of SQL on a SQL SP4 box. Can someone please
>clarify a few things for me?
>1. Can this be done during productions hours - does it requre a reboot?
>2. Does it actually install another full version of SQL - I only have a
CD
>that has SQL 2000 on it so I would have to apply the SP 4 after the fact -
>will this affect the production instance default instance)
>3. Does it use a different service account to start?
>4. Can it use a second bound IP address?
>Any other tips I should be aware of? Thanks for your time.
>
>

Adding 2nd instance of SQL

I am adding a 2nd instance of SQL on a SQL SP4 box. Can someone please
clarify a few things for me?
1. Can this be done during productions hours - does it requre a reboot?
2. Does it actually install another full version of SQL - I only have a CD
that has SQL 2000 on it so I would have to apply the SP 4 after the fact -
will this affect the production instance default instance)
3. Does it use a different service account to start?
4. Can it use a second bound IP address?
Any other tips I should be aware of? Thanks for your time.Hi
"Bad Beagle" wrote:
> I am adding a 2nd instance of SQL on a SQL SP4 box. Can someone please
> clarify a few things for me?
> 1. Can this be done during productions hours - does it requre a reboot?
It should not require a re-boot, but it would not be a good idea to do it on
a production server whilst it is being used.
> 2. Does it actually install another full version of SQL - I only have a CD
> that has SQL 2000 on it so I would have to apply the SP 4 after the fact -
> will this affect the production instance default instance)
Yes you would need to apply a service pack separately.
> 3. Does it use a different service account to start?
This is however you configure it, the can be the same if required.
> 4. Can it use a second bound IP address?
You could do this via a firewall and filter on tcp/ip ports or possibly by
using the TCP/IP filtering in the advanced options of the network connection.
> Any other tips I should be aware of? Thanks for your time.
>
>
Having a second instance will use resources on this machine, you should not
(really) have a second instance on a production server if you can avoid it,
and certainly test/development instances should be kept separate.
John|||Hello,
Thank you for posting. Also, thanks very much to John for his contribution.
It seems that John has essentially answered all the questions appropriately.
You can install the instance without re-booting the system. Application of
SP4 does require a reboot. I would also recommend that, regardless, you do
reboot the system simply to refresh services and what not. You can
install the instance followed by SP4 then reboot.
My understanding is that the root of this question is "Can you do the
installation on a production server while it is being used?" While it
should work without issue, there are a number of reasons not to attempt
this. First, if something does go wrong, you may unexpectedly bring down
your production server while people are using it, thus potentially losing
data and incurring user and executive wrath: something we all generally
want to avoid. Secondly, and particularly with SP updates, installations
have been known to fail silently and return a successful message without
properly updating services. It's very much recommended to do any such type
of major administration while the database is not being accessed.
You can configure the service account either during the installation of the
SQL Server, or you can update it later through SQL Enterprise manager. As
John mentioned, you can set it to a different account or the same account
depending on your requirements.
You can bind each instance that you install to a separate port, but you can
not specify an IP address for each instance. Instead, the port for the
TCP/IP network protocal is dynamically configured during installation. As
John suggests you can manage this using NAT at your Router/Firewall. To
check/change the port for the instance, you can open SQL Enterprise Manger,
Right click the instance you want to change, select Properties > Network
Configuration... > TCP/IP > Properties...
John also brings up a very good point about the performance implications of
running an extra instance on a production server. Basically, when you add
an instance, all the following are replicated, taking up additional
resources:
> SQL Server database engine
> System and user databases.
> The SQL Server and SQL Server Agent services.
> The registry keys associated with the database engine and the SQL Server
and SQL Server Agent services.
> Network connection addresses
(*see:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_
ar_cs_9i5u.asp)
Please also review the BOL section on 'multiple instance of SQL Server' in
the index for BOL. See particularly the sections "best practices', 'memory
usage', and 'when to use' to better determine if installing separate
instances is actually in your best interest.
Hope this helps!
Sincerely,
Dana Brash [MSFT]
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
>From: "Bad Beagle" <maxwelli@.nospam.postalias>
>Subject: Adding 2nd instance of SQL
>Date: Fri, 13 Jan 2006 07:29:45 -0700
>Lines: 12
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <eScgO3EGGHA.3944@.tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 199.213.91.1
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:417520
>X-Tomcat-NG: microsoft.public.sqlserver.server
>I am adding a 2nd instance of SQL on a SQL SP4 box. Can someone please
>clarify a few things for me?
>1. Can this be done during productions hours - does it requre a reboot?
>2. Does it actually install another full version of SQL - I only have a
CD
>that has SQL 2000 on it so I would have to apply the SP 4 after the fact -
>will this affect the production instance default instance)
>3. Does it use a different service account to start?
>4. Can it use a second bound IP address?
>Any other tips I should be aware of? Thanks for your time.
>
>|||Hi,
Just want to say Hi, and I was wondering how everything is going. If
anything is unclear, please let me know. It is my pleasure to be of
assistance.
Hope this helps!
Sincerely,
Dana Brash
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
>From: "Bad Beagle" <maxwelli@.nospam.postalias>
>Subject: Adding 2nd instance of SQL
>Date: Fri, 13 Jan 2006 07:29:45 -0700
>Lines: 12
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <eScgO3EGGHA.3944@.tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 199.213.91.1
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:417520
>X-Tomcat-NG: microsoft.public.sqlserver.server
>I am adding a 2nd instance of SQL on a SQL SP4 box. Can someone please
>clarify a few things for me?
>1. Can this be done during productions hours - does it requre a reboot?
>2. Does it actually install another full version of SQL - I only have a
CD
>that has SQL 2000 on it so I would have to apply the SP 4 after the fact -
>will this affect the production instance default instance)
>3. Does it use a different service account to start?
>4. Can it use a second bound IP address?
>Any other tips I should be aware of? Thanks for your time.
>
>|||Hi,
Just a followup on this post. I am wondering if you have any questions or
concerns about this issue. If you need further assistance, please do not
hesitate to let me know.
Hope this helps!
Sincerely,
Dana Brash
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/technicalsupport/supportoverview/40010469
Others: https://partner.microsoft.com/US/technicalsupport/supportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
>From: "Bad Beagle" <maxwelli@.nospam.postalias>
>Subject: Adding 2nd instance of SQL
>Date: Fri, 13 Jan 2006 07:29:45 -0700
>Lines: 12
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <eScgO3EGGHA.3944@.tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 199.213.91.1
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:417520
>X-Tomcat-NG: microsoft.public.sqlserver.server
>I am adding a 2nd instance of SQL on a SQL SP4 box. Can someone please
>clarify a few things for me?
>1. Can this be done during productions hours - does it requre a reboot?
>2. Does it actually install another full version of SQL - I only have a
CD
>that has SQL 2000 on it so I would have to apply the SP 4 after the fact -
>will this affect the production instance default instance)
>3. Does it use a different service account to start?
>4. Can it use a second bound IP address?
>Any other tips I should be aware of? Thanks for your time.
>
>

Adding 2nd instance of SQL

I am adding a 2nd instance of SQL on a SQL SP4 box. Can someone please
clarify a few things for me?
1. Can this be done during productions hours - does it requre a reboot?
2. Does it actually install another full version of SQL - I only have a CD
that has SQL 2000 on it so I would have to apply the SP 4 after the fact -
will this affect the production instance default instance)
3. Does it use a different service account to start?
4. Can it use a second bound IP address?
Any other tips I should be aware of? Thanks for your time.Hi
"Bad Beagle" wrote:

> I am adding a 2nd instance of SQL on a SQL SP4 box. Can someone please
> clarify a few things for me?
> 1. Can this be done during productions hours - does it requre a reboot?
It should not require a re-boot, but it would not be a good idea to do it on
a production server whilst it is being used.

> 2. Does it actually install another full version of SQL - I only have a C
D
> that has SQL 2000 on it so I would have to apply the SP 4 after the fact -
> will this affect the production instance default instance)
Yes you would need to apply a service pack separately.

> 3. Does it use a different service account to start?
This is however you configure it, the can be the same if required.

> 4. Can it use a second bound IP address?
You could do this via a firewall and filter on tcp/ip ports or possibly by
using the TCP/IP filtering in the advanced options of the network connection.">
> Any other tips I should be aware of? Thanks for your time.
>
>
Having a second instance will use resources on this machine, you should not
(really) have a second instance on a production server if you can avoid it,
and certainly test/development instances should be kept separate.
John|||Hello,
Thank you for posting. Also, thanks very much to John for his contribution.
It seems that John has essentially answered all the questions appropriately.
You can install the instance without re-booting the system. Application of
SP4 does require a reboot. I would also recommend that, regardless, you do
reboot the system simply to refresh services and what not. You can
install the instance followed by SP4 then reboot.
My understanding is that the root of this question is "Can you do the
installation on a production server while it is being used?" While it
should work without issue, there are a number of reasons not to attempt
this. First, if something does go wrong, you may unexpectedly bring down
your production server while people are using it, thus potentially losing
data and incurring user and executive wrath: something we all generally
want to avoid. Secondly, and particularly with SP updates, installations
have been known to fail silently and return a successful message without
properly updating services. It's very much recommended to do any such type
of major administration while the database is not being accessed.
You can configure the service account either during the installation of the
SQL Server, or you can update it later through SQL Enterprise manager. As
John mentioned, you can set it to a different account or the same account
depending on your requirements.
You can bind each instance that you install to a separate port, but you can
not specify an IP address for each instance. Instead, the port for the
TCP/IP network protocal is dynamically configured during installation. As
John suggests you can manage this using NAT at your Router/Firewall. To
check/change the port for the instance, you can open SQL Enterprise Manger,
Right click the instance you want to change, select Properties > Network
Configuration... > TCP/IP > Properties...
John also brings up a very good point about the performance implications of
running an extra instance on a production server. Basically, when you add
an instance, all the following are replicated, taking up additional
resources:

> SQL Server database engine
> System and user databases.
> The SQL Server and SQL Server Agent services.
> The registry keys associated with the database engine and the SQL Server
and SQL Server Agent services.
> Network connection addresses
(*see:
http://msdn.microsoft.com/library/d...-us/architec/8_
ar_cs_9i5u.asp)
Please also review the BOL section on 'multiple instance of SQL Server' in
the index for BOL. See particularly the sections "best practices', 'memory
usage', and 'when to use' to better determine if installing separate
instances is actually in your best interest.
Hope this helps!
Sincerely,
Dana Brash [MSFT]
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "Bad Beagle" <maxwelli@.nospam.postalias>
>Subject: Adding 2nd instance of SQL
>Date: Fri, 13 Jan 2006 07:29:45 -0700
>Lines: 12
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <eScgO3EGGHA.3944@.tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 199.213.91.1
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:417520
>X-Tomcat-NG: microsoft.public.sqlserver.server
>I am adding a 2nd instance of SQL on a SQL SP4 box. Can someone please
>clarify a few things for me?
>1. Can this be done during productions hours - does it requre a reboot?
>2. Does it actually install another full version of SQL - I only have a
CD
>that has SQL 2000 on it so I would have to apply the SP 4 after the fact -
>will this affect the production instance default instance)
>3. Does it use a different service account to start?
>4. Can it use a second bound IP address?
>Any other tips I should be aware of? Thanks for your time.
>
>|||Hi,
Just want to say Hi, and I was wondering how everything is going. If
anything is unclear, please let me know. It is my pleasure to be of
assistance.
Hope this helps!
Sincerely,
Dana Brash
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...erview/40010469
Others: https://partner.microsoft.com/US/te...upportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "Bad Beagle" <maxwelli@.nospam.postalias>
>Subject: Adding 2nd instance of SQL
>Date: Fri, 13 Jan 2006 07:29:45 -0700
>Lines: 12
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <eScgO3EGGHA.3944@.tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 199.213.91.1
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:417520
>X-Tomcat-NG: microsoft.public.sqlserver.server
>I am adding a 2nd instance of SQL on a SQL SP4 box. Can someone please
>clarify a few things for me?
>1. Can this be done during productions hours - does it requre a reboot?
>2. Does it actually install another full version of SQL - I only have a
CD
>that has SQL 2000 on it so I would have to apply the SP 4 after the fact -
>will this affect the production instance default instance)
>3. Does it use a different service account to start?
>4. Can it use a second bound IP address?
>Any other tips I should be aware of? Thanks for your time.
>
>|||Hi,
Just a followup on this post. I am wondering if you have any questions or
concerns about this issue. If you need further assistance, please do not
hesitate to let me know.
Hope this helps!
Sincerely,
Dana Brash
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/te...erview/40010469
Others: https://partner.microsoft.com/US/te...upportoverview/
If you are outside the United States, please visit our International
Support page: http://support.microsoft.com/common/international.aspx.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "Bad Beagle" <maxwelli@.nospam.postalias>
>Subject: Adding 2nd instance of SQL
>Date: Fri, 13 Jan 2006 07:29:45 -0700
>Lines: 12
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>X-RFC2646: Format=Flowed; Original
>Message-ID: <eScgO3EGGHA.3944@.tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 199.213.91.1
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.server:417520
>X-Tomcat-NG: microsoft.public.sqlserver.server
>I am adding a 2nd instance of SQL on a SQL SP4 box. Can someone please
>clarify a few things for me?
>1. Can this be done during productions hours - does it requre a reboot?
>2. Does it actually install another full version of SQL - I only have a
CD
>that has SQL 2000 on it so I would have to apply the SP 4 after the fact -
>will this affect the production instance default instance)
>3. Does it use a different service account to start?
>4. Can it use a second bound IP address?
>Any other tips I should be aware of? Thanks for your time.
>
>sql

Add New Database Error "object reference not set to an instance of an object"

Hi,

I'm new to SQL database.

When I add a new item to project in VS2005: Project-->Add New Item --> Sql Database I got a error msg "object reference not set to an instance of an object" after click "Add" button. The SQL Server Express is running. How do I fix this problem?

Any help would be appreceiated.

CO22006

Moving to the SQL forum.

-Tim <MSFT>

Add And Query Linked Server To ADAM Instance...

I was not sure if this was the best SQL Server newsgroup to post this
question to but I thought I would start here.
I would like to add a linked server to an ADAM instance and then be able to
execute queries against this linked server. It looks like I can add the
linked server but I am not sure if I am doing it right. When I try to
execute a query, I receive the following:
An error occurred while preparing the query ... for execution against OLE DB
provider "ADsDSOObject" for linked server ...
I have not been able to get around this error. From what I have read, I am
getting the impression that this is a security issue. I have tried to add
logons to the linked server but again, I am not sure if I am doing this
right. Most of the articles seem to lead me in the right direction but there
is something I am not doing correctly.
Any help with this will be most appreciated.
By the way, I am using SQL Server 2005.
Thank you,
JasonWhen you created the linked server did you define the security at all? Can
you show the query you were trying to execute?
"Jason Richmeier" wrote:
> I was not sure if this was the best SQL Server newsgroup to post this
> question to but I thought I would start here.
> I would like to add a linked server to an ADAM instance and then be able to
> execute queries against this linked server. It looks like I can add the
> linked server but I am not sure if I am doing it right. When I try to
> execute a query, I receive the following:
> An error occurred while preparing the query ... for execution against OLE DB
> provider "ADsDSOObject" for linked server ...
> I have not been able to get around this error. From what I have read, I am
> getting the impression that this is a security issue. I have tried to add
> logons to the linked server but again, I am not sure if I am doing this
> right. Most of the articles seem to lead me in the right direction but there
> is something I am not doing correctly.
> Any help with this will be most appreciated.
> By the way, I am using SQL Server 2005.
> Thank you,
> Jason

add an sql 2000 instance to a production server

Hi,
If I add an sql 2000 instance to a existing prod sql box used as a
developping sql instance.
The developers don't need to tough the production box..
Is it feasible? it will reduce the production performance?
What's the side effect?
What about creating a virtual server -- 2-3 virtual sql servers in a one
physical box.
Thanksmecn wrote:
> Hi,
> If I add an sql 2000 instance to a existing prod sql box used as a
> developping sql instance.
> The developers don't need to tough the production box..
> Is it feasible? it will reduce the production performance?
Don't do that. Production and developing (or test) environment should be
separated. Separation means that there is no influence between them.
Unfortunately, when two instances are installed on the same server, one
instance can easily affect performance of other instance.
> What's the side effect?
When you add another (dev) instance, it will use common system
resources. Dev instance will consume RAM memory potentially available
for prod instance, it will also utilize processor(s) and IO.
IMHO it's a risky move.
> What about creating a virtual server -- 2-3 virtual sql servers in a one
> physical box.
Better idea, because virtualization introduces much higher separation
level, but I think that's still not enough. Let production SQL Server
work on dedicated machine.
Best regards,
Marcin Guzowski
http://guzowski.info|||Thanks. I got it.
"Marcin A. Guzowski" <tu_wstaw_moje_imie@.guzowski.info> wrote in message
news:f5ufol$grr$1@.news.onet.pl...
> mecn wrote:
>> Hi,
>> If I add an sql 2000 instance to a existing prod sql box used as a
>> developping sql instance.
>> The developers don't need to tough the production box..
>> Is it feasible? it will reduce the production performance?
> Don't do that. Production and developing (or test) environment should be
> separated. Separation means that there is no influence between them.
> Unfortunately, when two instances are installed on the same server, one
> instance can easily affect performance of other instance.
>> What's the side effect?
> When you add another (dev) instance, it will use common system resources.
> Dev instance will consume RAM memory potentially available for prod
> instance, it will also utilize processor(s) and IO.
> IMHO it's a risky move.
>> What about creating a virtual server -- 2-3 virtual sql servers in a one
>> physical box.
> Better idea, because virtualization introduces much higher separation
> level, but I think that's still not enough. Let production SQL Server work
> on dedicated machine.
>
> --
> Best regards,
> Marcin Guzowski
> http://guzowski.info|||Do I need more sql licenses for virtual servers
"mecn" <mecn2002@.yahoo.com> wrote in message
news:uWMC86OuHHA.1184@.TK2MSFTNGP04.phx.gbl...
> Hi,
> If I add an sql 2000 instance to a existing prod sql box used as a
> developping sql instance.
> The developers don't need to tough the production box..
> Is it feasible? it will reduce the production performance?
> What's the side effect?
> What about creating a virtual server -- 2-3 virtual sql servers in a one
> physical box.
> Thanks
>|||mecn wrote:
> Do I need more sql licenses for virtual servers
I don't know if it is true for SQL Server 2000 (probably not), but in
SQL Server 2005 it depends on SQL Server version (edition). If you have
SQL Server 2005 Enterprise Edition, you don't need additional licenses
for each virtual server.
In other cases, you must buy new licenses.
Best regards,
Marcin Guzowski
http://guzowski.info|||Thanks a lot dfor your help!!
"Marcin A. Guzowski" <tu_wstaw_moje_imie@.guzowski.info> wrote in message
news:f5ui6o$pu8$1@.news.onet.pl...
> mecn wrote:
>> Do I need more sql licenses for virtual servers
> I don't know if it is true for SQL Server 2000 (probably not), but in SQL
> Server 2005 it depends on SQL Server version (edition). If you have SQL
> Server 2005 Enterprise Edition, you don't need additional licenses for
> each virtual server.
> In other cases, you must buy new licenses.
>
> --
> Best regards,
> Marcin Guzowski
> http://guzowski.info

add an sql 2000 instance to a production server

Hi,
If I add an sql 2000 instance to a existing prod sql box used as a
developping sql instance.
The developers don't need to tough the production box..
Is it feasible? it will reduce the production performance?
What's the side effect?
What about creating a virtual server -- 2-3 virtual sql servers in a one
physical box.
Thanks
mecn wrote:
> Hi,
> If I add an sql 2000 instance to a existing prod sql box used as a
> developping sql instance.
> The developers don't need to tough the production box..
> Is it feasible? it will reduce the production performance?
Don't do that. Production and developing (or test) environment should be
separated. Separation means that there is no influence between them.
Unfortunately, when two instances are installed on the same server, one
instance can easily affect performance of other instance.

> What's the side effect?
When you add another (dev) instance, it will use common system
resources. Dev instance will consume RAM memory potentially available
for prod instance, it will also utilize processor(s) and IO.
IMHO it's a risky move.

> What about creating a virtual server -- 2-3 virtual sql servers in a one
> physical box.
Better idea, because virtualization introduces much higher separation
level, but I think that's still not enough. Let production SQL Server
work on dedicated machine.
Best regards,
Marcin Guzowski
http://guzowski.info
|||Thanks. I got it.
"Marcin A. Guzowski" <tu_wstaw_moje_imie@.guzowski.info> wrote in message
news:f5ufol$grr$1@.news.onet.pl...
> mecn wrote:
> Don't do that. Production and developing (or test) environment should be
> separated. Separation means that there is no influence between them.
> Unfortunately, when two instances are installed on the same server, one
> instance can easily affect performance of other instance.
>
> When you add another (dev) instance, it will use common system resources.
> Dev instance will consume RAM memory potentially available for prod
> instance, it will also utilize processor(s) and IO.
> IMHO it's a risky move.
>
> Better idea, because virtualization introduces much higher separation
> level, but I think that's still not enough. Let production SQL Server work
> on dedicated machine.
>
> --
> Best regards,
> Marcin Guzowski
> http://guzowski.info
|||Do I need more sql licenses for virtual servers
"mecn" <mecn2002@.yahoo.com> wrote in message
news:uWMC86OuHHA.1184@.TK2MSFTNGP04.phx.gbl...
> Hi,
> If I add an sql 2000 instance to a existing prod sql box used as a
> developping sql instance.
> The developers don't need to tough the production box..
> Is it feasible? it will reduce the production performance?
> What's the side effect?
> What about creating a virtual server -- 2-3 virtual sql servers in a one
> physical box.
> Thanks
>
|||mecn wrote:
> Do I need more sql licenses for virtual servers
I don't know if it is true for SQL Server 2000 (probably not), but in
SQL Server 2005 it depends on SQL Server version (edition). If you have
SQL Server 2005 Enterprise Edition, you don't need additional licenses
for each virtual server.
In other cases, you must buy new licenses.
Best regards,
Marcin Guzowski
http://guzowski.info
|||Thanks a lot dfor your help!!
"Marcin A. Guzowski" <tu_wstaw_moje_imie@.guzowski.info> wrote in message
news:f5ui6o$pu8$1@.news.onet.pl...
> mecn wrote:
> I don't know if it is true for SQL Server 2000 (probably not), but in SQL
> Server 2005 it depends on SQL Server version (edition). If you have SQL
> Server 2005 Enterprise Edition, you don't need additional licenses for
> each virtual server.
> In other cases, you must buy new licenses.
>
> --
> Best regards,
> Marcin Guzowski
> http://guzowski.info

add an sql 2000 instance to a production server

Hi,
If I add an sql 2000 instance to a existing prod sql box used as a
developping sql instance.
The developers don't need to tough the production box..
Is it feasible? it will reduce the production performance?
What's the side effect?
What about creating a virtual server -- 2-3 virtual sql servers in a one
physical box.
Thanksmecn wrote:
> Hi,
> If I add an sql 2000 instance to a existing prod sql box used as a
> developping sql instance.
> The developers don't need to tough the production box..
> Is it feasible? it will reduce the production performance?
Don't do that. Production and developing (or test) environment should be
separated. Separation means that there is no influence between them.
Unfortunately, when two instances are installed on the same server, one
instance can easily affect performance of other instance.

> What's the side effect?
When you add another (dev) instance, it will use common system
resources. Dev instance will consume RAM memory potentially available
for prod instance, it will also utilize processor(s) and IO.
IMHO it's a risky move.

> What about creating a virtual server -- 2-3 virtual sql servers in a one
> physical box.
Better idea, because virtualization introduces much higher separation
level, but I think that's still not enough. Let production SQL Server
work on dedicated machine.
Best regards,
Marcin Guzowski
http://guzowski.info|||Thanks. I got it.
"Marcin A. Guzowski" <tu_wstaw_moje_imie@.guzowski.info> wrote in message
news:f5ufol$grr$1@.news.onet.pl...
> mecn wrote:
> Don't do that. Production and developing (or test) environment should be
> separated. Separation means that there is no influence between them.
> Unfortunately, when two instances are installed on the same server, one
> instance can easily affect performance of other instance.
>
> When you add another (dev) instance, it will use common system resources.
> Dev instance will consume RAM memory potentially available for prod
> instance, it will also utilize processor(s) and IO.
> IMHO it's a risky move.
>
> Better idea, because virtualization introduces much higher separation
> level, but I think that's still not enough. Let production SQL Server work
> on dedicated machine.
>
> --
> Best regards,
> Marcin Guzowski
> http://guzowski.info|||Do I need more sql licenses for virtual servers
"mecn" <mecn2002@.yahoo.com> wrote in message
news:uWMC86OuHHA.1184@.TK2MSFTNGP04.phx.gbl...
> Hi,
> If I add an sql 2000 instance to a existing prod sql box used as a
> developping sql instance.
> The developers don't need to tough the production box..
> Is it feasible? it will reduce the production performance?
> What's the side effect?
> What about creating a virtual server -- 2-3 virtual sql servers in a one
> physical box.
> Thanks
>|||mecn wrote:
> Do I need more sql licenses for virtual servers
I don't know if it is true for SQL Server 2000 (probably not), but in
SQL Server 2005 it depends on SQL Server version (edition). If you have
SQL Server 2005 Enterprise Edition, you don't need additional licenses
for each virtual server.
In other cases, you must buy new licenses.
Best regards,
Marcin Guzowski
http://guzowski.info|||Thanks a lot dfor your help!!
"Marcin A. Guzowski" <tu_wstaw_moje_imie@.guzowski.info> wrote in message
news:f5ui6o$pu8$1@.news.onet.pl...
> mecn wrote:
> I don't know if it is true for SQL Server 2000 (probably not), but in SQL
> Server 2005 it depends on SQL Server version (edition). If you have SQL
> Server 2005 Enterprise Edition, you don't need additional licenses for
> each virtual server.
> In other cases, you must buy new licenses.
>
> --
> Best regards,
> Marcin Guzowski
> http://guzowski.info

Add a 3rd node to a 2 instance active/active cluster

If I add a 3rd node to an already existing 2 node active/active cluster, do
I have to take the other 2 instances offline as I configure the 3rd node?
I have never configured a cluster before, but I am under the assumption that
when you build a cluster, each nodes should be able to map to the shared
resource drives and due to that, I would have to take the other instances
offline.
Thanks
Not that it matters, but SQL2K or 2K5? I've just been doing this the
past couple of days and have some tips for you if 2K...
But to answer your question - you shouldn't have to take them offline.
On Feb 4, 12:24 pm, "Hassan" <has...@.hotmail.com> wrote:
> If I add a 3rd node to an already existing 2 node active/active cluster, do
> I have to take the other 2 instances offline as I configure the 3rd node?
> I have never configured a cluster before, but I am under the assumption that
> when you build a cluster, each nodes should be able to map to the shared
> resource drives and due to that, I would have to take the other instances
> offline.
> Thanks
|||Im all ears for tips.. so shoot away.. Can your tips not apply for 2K5 ?
<unc27932@.yahoo.com> wrote in message
news:1170779511.734049.110890@.s48g2000cws.googlegr oups.com...
> Not that it matters, but SQL2K or 2K5? I've just been doing this the
> past couple of days and have some tips for you if 2K...
> But to answer your question - you shouldn't have to take them offline.
> On Feb 4, 12:24 pm, "Hassan" <has...@.hotmail.com> wrote:
>
|||It will take the instances offline, although SS2K5 minimizes this much more.
A bigger issue is that before the new node will be able to host the
resources, you will need to patch it to the same build level as the other
two nodes.
The add a node step only lays out the RTM binaries.
Sincerely,
Anthony Thomas

"Hassan" <hassan@.hotmail.com> wrote in message
news:%23kRF9AmSHHA.1364@.TK2MSFTNGP06.phx.gbl...[vbcol=seagreen]
> Im all ears for tips.. so shoot away.. Can your tips not apply for 2K5 ?
> <unc27932@.yahoo.com> wrote in message
> news:1170779511.734049.110890@.s48g2000cws.googlegr oups.com...
cluster,[vbcol=seagreen]
node?[vbcol=seagreen]
shared[vbcol=seagreen]
instances
>

Ad: Problems Creating Instance in SQL 2005 management studio

Hello all,
Thanks in advance for any help you can provide.
I am having a problem creating a new NS instance using SQL 2005 management studio.
I am using the database element in my instance and application xml files like this,
in order to create the NS application in an existing database.
<Database>
<DatabaseName>%databasename%</DatabaseName>
<SchemaName>%schemaname%</SchemaName>
</Database>
the problem that I am having is that if I encounter an error somewhere in the process of creating this new instance the instance name and schema name I specified are still bound somewhere, and if I correct for the error and try to create the instance again, I receive a new error saying that there is already an instance with my instance name, or using the schema name.
If I try to list versions it tells me there are no instances, yet if I try to add a new instance it tells me there is already an instance using my instance name.
I have tried searching master database tables and views for anywhere where it might be stored, also tried poking around most of management studio and the registry, and just can not seem to find where it is remembering that I had tried to create this instance before.
It is like it is partially creating the instance, running into an error, and then not rolling back its changes somewhere.

Any help would be very much appreciated

-Derek-

Web Services Integration Manager

TempWorks Software

Si Vis Pacem, Para Bellum.

"Those who profess to favor freedom, and yet depreciate agitation, are men who want crops without plowing up the ground. They want rain without thunder and lightning. They want the ocean without the awful roar of its many waters. Power concedes nothing without demand. It never did and it never will." - Frederick Douglass

additional error information.
I tried to remove the database and restore from a backup, and yet it still believe the instance name is in use.
I notice it seems to be checking the NS InstanceMetaData for existing instances on this server...
"Microsoft.SqlServer.NotificationServices.Common.InstanceMetadata.CheckInstanceNameInUse"
anyone know where this metadata is ?

===================================

The specified name is used by another Notification Services instance on the server. Specify a different instance name.
Instance Name: TWNSinstance
Server Name: derekxps (Microsoft.SqlServer.NotificationServices)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=NSEventStrings&EvtID=DuplicateInstanceName&LinkId=20476

Program Location:

at Microsoft.SqlServer.NotificationServices.Common.InstanceMetadata.CheckInstanceNameInUse(SqlConnection sqlConnection, NSInstance instance)
at Microsoft.SqlServer.NotificationServices.Common.InstanceMetadata.Add(NSInstance instance)
at Microsoft.SqlServer.NotificationServices.Common.NSDatabaseCreator.Create(NSDBState dbState, SqlDatabaseAttributes databaseAttributes, List`1 createdStates)
at Microsoft.SqlServer.NotificationServices.Common.InstanceCompiler.CreateDatabaseInfrastructure(Instance instance, NSSecureString argumentKey, NSInstance& nsInstance, Dictionary`2& nsApplications)
at Microsoft.SqlServer.NotificationServices.Common.InstanceCompiler.Create(Instance instance, NSSecureString argumentKey, Boolean uiReporting)
at Microsoft.SqlServer.NotificationServices.Common.InstanceCompiler.Create(NSSecureString sqlUserName, NSSecureString sqlPassword, String configFile, NSSecureString argumentKey, StringDictionary substitutions, Boolean uiReporting, String enforcedSqlServerSystem)
at Microsoft.SqlServer.Management.NotificationServicesUI.CreateInstanceGeneral.PerformCreate()|||

Hi Derek -

SQLNS 2005 stores its metadata in the MSDB database. Run this script in SSMS and see if your failed instance/application are listed.

USE MSDB

GO

SELECT*FROM NS90.NSInstanceInfo

SELECT*FROM NS90.NSApplicationInfo

HTH..

Joe

|||Thanks Joe,
I did find the instance names and schema names that it had "eaten" in there. cleared them and was able to install with the instance name I wanted.
Thanks for your help!

-Derek-

Ad: Problems Creating Instance in SQL 2005 management studio

Hello all,

Thanks in advance for any help you can provide.

I am having a problem creating a new NS instance using SQL 2005 management

studio.

I am using the database element in my instance and application xml files like

this,

in order to create the NS application in an existing database.

<Database>

<DatabaseName>%databasename%</DatabaseName>

<SchemaName>%schemaname%</SchemaName>

</Database>

the problem that I am having is that if I encounter an error somewhere in the

process of creating this new instance the instance name and schema name I

specified are still bound somewhere, and if I correct for the error and try to

create the instance again, I receive a new error saying that there is already

an instance with my instance name, or using the schema name.

If I try to list versions it tells me there are no instances, yet if I try to

add a new instance it tells me there is already an instance using my instance

name.

I have tried searching master database tables and views for anywhere

where it might be stored, also tried poking around most of management studio

and the registry, and just can not seem to find where it is remembering that I

had tried to create this instance before.

It is like it is partially creating the instance, running into an error, and

then not rolling back its changes somewhere.
Any help would be very much appreciated

-Derek-

Web Services

Integration Manager

TempWorks Software

Si Vis Pacem, Para Bellum.

"Those who profess to favor freedom, and yet depreciate agitation,

are men who want crops without plowing up the ground. They want rain without

thunder and lightning. They want the ocean without the awful roar of its

many waters. Power concedes nothing without demand. It never did and it

never will." - Frederick Douglass

additional error information.
I tried to remove the database and restore from a backup, and yet it still believe the instance name is in use.
I notice it seems to be checking the NS InstanceMetaData for existing instances on this server...
"Microsoft.SqlServer.NotificationServices.Common.InstanceMetadata.CheckInstanceNameInUse"
anyone know where this metadata is ?

===================================

The specified name is used by another Notification Services instance on the server. Specify a different instance name.
Instance Name: TWNSinstance
Server Name: derekxps (Microsoft.SqlServer.NotificationServices)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=NSEventStrings&EvtID=DuplicateInstanceName&LinkId=20476

Program Location:

at Microsoft.SqlServer.NotificationServices.Common.InstanceMetadata.CheckInstanceNameInUse(SqlConnection sqlConnection, NSInstance instance)
at Microsoft.SqlServer.NotificationServices.Common.InstanceMetadata.Add(NSInstance instance)
at Microsoft.SqlServer.NotificationServices.Common.NSDatabaseCreator.Create(NSDBState dbState, SqlDatabaseAttributes databaseAttributes, List`1 createdStates)
at Microsoft.SqlServer.NotificationServices.Common.InstanceCompiler.CreateDatabaseInfrastructure(Instance instance, NSSecureString argumentKey, NSInstance& nsInstance, Dictionary`2& nsApplications)
at Microsoft.SqlServer.NotificationServices.Common.InstanceCompiler.Create(Instance instance, NSSecureString argumentKey, Boolean uiReporting)
at Microsoft.SqlServer.NotificationServices.Common.InstanceCompiler.Create(NSSecureString sqlUserName, NSSecureString sqlPassword, String configFile, NSSecureString argumentKey, StringDictionary substitutions, Boolean uiReporting, String enforcedSqlServerSystem)
at Microsoft.SqlServer.Management.NotificationServicesUI.CreateInstanceGeneral.PerformCreate()|||

Hi Derek -

SQLNS 2005 stores its metadata in the MSDB database. Run this script in SSMS and see if your failed instance/application are listed.

USE MSDB

GO

SELECT * FROM NS90.NSInstanceInfo

SELECT * FROM NS90.NSApplicationInfo

HTH..

Joe

|||Thanks Joe,
I did find the instance names and schema names that it had "eaten" in there. cleared them and was able to install with the instance name I wanted.
Thanks for your help!

-Derek-

Ad: Answer Worked!

Hello all,
Thanks in advance for any help you can provide.
I am having a problem creating a new NS instance using SQL 2005 management studio.
I am using the database element in my instance and application xml files like this,
in order to create the NS application in an existing database.
<Database>
<DatabaseName>%databasename%</DatabaseName>
<SchemaName>%schemaname%</SchemaName>
</Database>
the problem that I am having is that if I encounter an error somewhere in the process of creating this new instance the instance name and schema name I specified are still bound somewhere, and if I correct for the error and try to create the instance again, I receive a new error saying that there is already an instance with my instance name, or using the schema name.
If I try to list versions it tells me there are no instances, yet if I try to add a new instance it tells me there is already an instance using my instance name.
I have tried searching master database tables and views for anywhere where it might be stored, also tried poking around most of management studio and the registry, and just can not seem to find where it is remembering that I had tried to create this instance before.
It is like it is partially creating the instance, running into an error, and then not rolling back its changes somewhere.

Any help would be very much appreciated

-Derek-

Web Services Integration Manager

TempWorks Software

Si Vis Pacem, Para Bellum.

"Those who profess to favor freedom, and yet depreciate agitation, are men who want crops without plowing up the ground. They want rain without thunder and lightning. They want the ocean without the awful roar of its many waters. Power concedes nothing without demand. It never did and it never will." - Frederick Douglass

additional error information.
I tried to remove the database and restore from a backup, and yet it still believe the instance name is in use.
I notice it seems to be checking the NS InstanceMetaData for existing instances on this server...
"Microsoft.SqlServer.NotificationServices.Common.InstanceMetadata.CheckInstanceNameInUse"
anyone know where this metadata is ?

===================================

The specified name is used by another Notification Services instance on the server. Specify a different instance name.
Instance Name: TWNSinstance
Server Name: derekxps (Microsoft.SqlServer.NotificationServices)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=NSEventStrings&EvtID=DuplicateInstanceName&LinkId=20476

Program Location:

at Microsoft.SqlServer.NotificationServices.Common.InstanceMetadata.CheckInstanceNameInUse(SqlConnection sqlConnection, NSInstance instance)
at Microsoft.SqlServer.NotificationServices.Common.InstanceMetadata.Add(NSInstance instance)
at Microsoft.SqlServer.NotificationServices.Common.NSDatabaseCreator.Create(NSDBState dbState, SqlDatabaseAttributes databaseAttributes, List`1 createdStates)
at Microsoft.SqlServer.NotificationServices.Common.InstanceCompiler.CreateDatabaseInfrastructure(Instance instance, NSSecureString argumentKey, NSInstance& nsInstance, Dictionary`2& nsApplications)
at Microsoft.SqlServer.NotificationServices.Common.InstanceCompiler.Create(Instance instance, NSSecureString argumentKey, Boolean uiReporting)
at Microsoft.SqlServer.NotificationServices.Common.InstanceCompiler.Create(NSSecureString sqlUserName, NSSecureString sqlPassword, String configFile, NSSecureString argumentKey, StringDictionary substitutions, Boolean uiReporting, String enforcedSqlServerSystem)
at Microsoft.SqlServer.Management.NotificationServicesUI.CreateInstanceGeneral.PerformCreate()|||

Hi Derek -

SQLNS 2005 stores its metadata in the MSDB database. Run this script in SSMS and see if your failed instance/application are listed.

USE MSDB

GO

SELECT*FROM NS90.NSInstanceInfo

SELECT*FROM NS90.NSApplicationInfo

HTH..

Joe

|||Thanks Joe,
I did find the instance names and schema names that it had "eaten" in there. cleared them and was able to install with the instance name I wanted.
Thanks for your help!

-Derek-