How can I determine if the sql instance I have is the default instance or a
named instance?
Secondly how do I adjust a named instance to be the default instance?
Lastly if I have 2 servers configured identically (one working as a
production server and the other as a backup server) and a problem arises with
the production server can I simply just switch IP's and have the backup
server quickly become the production? Is this a standard practice Or will I
have to preform more adjustments?
Thanks
Dre
SELECT @.@.Servername (<InstanceName> for default,
Servername\<InstanceName> for named ones)
"Secondly how do I adjust a named instance to be the default instance?"
AFAIK thats not possible, you can only deinstall and reinstall
everything cause even the Windows services have to be rebuilt from the
setup.
HTH, jens Suessmeyer-
|||Two servers cannot have same name, so you to name them different with
different IP addresses. When the production server fails you have to
update your internal DNS for production server to point backup server.
Showing posts with label instance. Show all posts
Showing posts with label instance. Show all posts
Thursday, March 29, 2012
Default instance VS Named instance
If you have a choice to pick default instance or named instance, which one
will you choose and why ?
One saying is named instance provides more descriptions
to the DBAs if they need to managed many DBs.
Hi
Having multiple instances on a single machine will use up additional
resources, but there are valid reasons to do so, including ones related to
secutity an access. Having a single named instance on a machine, is probably
a personal preference, although you will always need to know and specify the
instance name when connecting to it.
I seem to remember that MSDE will only install as a named instance, but can
find where I saw it!
John
"Angus" wrote:
> If you have a choice to pick default instance or named instance, which one
> will you choose and why ?
> One saying is named instance provides more descriptions
> to the DBAs if they need to managed many DBs.
|||MSDE can run under and be installed under either. The problem is that it
typically is installed where another instance is already running.
Some applications can not connect to a named instance, the "\" in the server
name throws them off for some reason.
Other than that, it makes no difference. If you are running multiple
instances, you have to have a way to distinguish them and their respectie
binaries and services, thus the concept of a named instance to begin with.
Sincerely,
Anthony Thomas
"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:EF5564B6-0087-408C-9DE4-B9792CF7BB31@.microsoft.com...
Hi
Having multiple instances on a single machine will use up additional
resources, but there are valid reasons to do so, including ones related to
secutity an access. Having a single named instance on a machine, is probably
a personal preference, although you will always need to know and specify the
instance name when connecting to it.
I seem to remember that MSDE will only install as a named instance, but can
find where I saw it!
John
"Angus" wrote:
> If you have a choice to pick default instance or named instance, which one
> will you choose and why ?
> One saying is named instance provides more descriptions
> to the DBAs if they need to managed many DBs.
will you choose and why ?
One saying is named instance provides more descriptions
to the DBAs if they need to managed many DBs.
Hi
Having multiple instances on a single machine will use up additional
resources, but there are valid reasons to do so, including ones related to
secutity an access. Having a single named instance on a machine, is probably
a personal preference, although you will always need to know and specify the
instance name when connecting to it.
I seem to remember that MSDE will only install as a named instance, but can
find where I saw it!
John
"Angus" wrote:
> If you have a choice to pick default instance or named instance, which one
> will you choose and why ?
> One saying is named instance provides more descriptions
> to the DBAs if they need to managed many DBs.
|||MSDE can run under and be installed under either. The problem is that it
typically is installed where another instance is already running.
Some applications can not connect to a named instance, the "\" in the server
name throws them off for some reason.
Other than that, it makes no difference. If you are running multiple
instances, you have to have a way to distinguish them and their respectie
binaries and services, thus the concept of a named instance to begin with.
Sincerely,
Anthony Thomas
"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:EF5564B6-0087-408C-9DE4-B9792CF7BB31@.microsoft.com...
Hi
Having multiple instances on a single machine will use up additional
resources, but there are valid reasons to do so, including ones related to
secutity an access. Having a single named instance on a machine, is probably
a personal preference, although you will always need to know and specify the
instance name when connecting to it.
I seem to remember that MSDE will only install as a named instance, but can
find where I saw it!
John
"Angus" wrote:
> If you have a choice to pick default instance or named instance, which one
> will you choose and why ?
> One saying is named instance provides more descriptions
> to the DBAs if they need to managed many DBs.
default instance vs named instance
How can I determine if the sql instance I have is the default instance or a
named instance?
Secondly how do I adjust a named instance to be the default instance?
Lastly if I have 2 servers configured identically (one working as a
production server and the other as a backup server) and a problem arises with
the production server can I simply just switch IP's and have the backup
server quickly become the production? Is this a standard practice Or will I
have to preform more adjustments?
Thanks
DreSELECT @.@.Servername (<InstanceName> for default,
Servername\<InstanceName> for named ones)
"Secondly how do I adjust a named instance to be the default instance?"
AFAIK thats not possible, you can only deinstall and reinstall
everything cause even the Windows services have to be rebuilt from the
setup.
HTH, jens Suessmeyer-|||Two servers cannot have same name, so you to name them different with
different IP addresses. When the production server fails you have to
update your internal DNS for production server to point backup server.
named instance?
Secondly how do I adjust a named instance to be the default instance?
Lastly if I have 2 servers configured identically (one working as a
production server and the other as a backup server) and a problem arises with
the production server can I simply just switch IP's and have the backup
server quickly become the production? Is this a standard practice Or will I
have to preform more adjustments?
Thanks
DreSELECT @.@.Servername (<InstanceName> for default,
Servername\<InstanceName> for named ones)
"Secondly how do I adjust a named instance to be the default instance?"
AFAIK thats not possible, you can only deinstall and reinstall
everything cause even the Windows services have to be rebuilt from the
setup.
HTH, jens Suessmeyer-|||Two servers cannot have same name, so you to name them different with
different IP addresses. When the production server fails you have to
update your internal DNS for production server to point backup server.
Default instance VS Named instance
If you have a choice to pick default instance or named instance, which one
will you choose and why ?
One saying is named instance provides more descriptions
to the DBAs if they need to managed many DBs.Hi
Having multiple instances on a single machine will use up additional
resources, but there are valid reasons to do so, including ones related to
secutity an access. Having a single named instance on a machine, is probably
a personal preference, although you will always need to know and specify the
instance name when connecting to it.
I seem to remember that MSDE will only install as a named instance, but can
find where I saw it!
John
"Angus" wrote:
> If you have a choice to pick default instance or named instance, which one
> will you choose and why ?
> One saying is named instance provides more descriptions
> to the DBAs if they need to managed many DBs.|||MSDE can run under and be installed under either. The problem is that it
typically is installed where another instance is already running.
Some applications can not connect to a named instance, the "\" in the server
name throws them off for some reason.
Other than that, it makes no difference. If you are running multiple
instances, you have to have a way to distinguish them and their respectie
binaries and services, thus the concept of a named instance to begin with.
Sincerely,
Anthony Thomas
"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:EF5564B6-0087-408C-9DE4-B9792CF7BB31@.microsoft.com...
Hi
Having multiple instances on a single machine will use up additional
resources, but there are valid reasons to do so, including ones related to
secutity an access. Having a single named instance on a machine, is probably
a personal preference, although you will always need to know and specify the
instance name when connecting to it.
I seem to remember that MSDE will only install as a named instance, but can
find where I saw it!
John
"Angus" wrote:
> If you have a choice to pick default instance or named instance, which one
> will you choose and why ?
> One saying is named instance provides more descriptions
> to the DBAs if they need to managed many DBs.
will you choose and why ?
One saying is named instance provides more descriptions
to the DBAs if they need to managed many DBs.Hi
Having multiple instances on a single machine will use up additional
resources, but there are valid reasons to do so, including ones related to
secutity an access. Having a single named instance on a machine, is probably
a personal preference, although you will always need to know and specify the
instance name when connecting to it.
I seem to remember that MSDE will only install as a named instance, but can
find where I saw it!
John
"Angus" wrote:
> If you have a choice to pick default instance or named instance, which one
> will you choose and why ?
> One saying is named instance provides more descriptions
> to the DBAs if they need to managed many DBs.|||MSDE can run under and be installed under either. The problem is that it
typically is installed where another instance is already running.
Some applications can not connect to a named instance, the "\" in the server
name throws them off for some reason.
Other than that, it makes no difference. If you are running multiple
instances, you have to have a way to distinguish them and their respectie
binaries and services, thus the concept of a named instance to begin with.
Sincerely,
Anthony Thomas
"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:EF5564B6-0087-408C-9DE4-B9792CF7BB31@.microsoft.com...
Hi
Having multiple instances on a single machine will use up additional
resources, but there are valid reasons to do so, including ones related to
secutity an access. Having a single named instance on a machine, is probably
a personal preference, although you will always need to know and specify the
instance name when connecting to it.
I seem to remember that MSDE will only install as a named instance, but can
find where I saw it!
John
"Angus" wrote:
> If you have a choice to pick default instance or named instance, which one
> will you choose and why ?
> One saying is named instance provides more descriptions
> to the DBAs if they need to managed many DBs.
default instance vs named instance
How can I determine if the sql instance I have is the default instance or a
named instance?
Secondly how do I adjust a named instance to be the default instance?
Lastly if I have 2 servers configured identically (one working as a
production server and the other as a backup server) and a problem arises wit
h
the production server can I simply just switch IP's and have the backup
server quickly become the production? Is this a standard practice Or will I
have to preform more adjustments?
Thanks
DreSELECT @.@.Servername (<InstanceName> for default,
Servername\<InstanceName> for named ones)
"Secondly how do I adjust a named instance to be the default instance?"
AFAIK thats not possible, you can only deinstall and reinstall
everything cause even the Windows services have to be rebuilt from the
setup.
HTH, jens Suessmeyer-|||Two servers cannot have same name, so you to name them different with
different IP addresses. When the production server fails you have to
update your internal DNS for production server to point backup server.sql
named instance?
Secondly how do I adjust a named instance to be the default instance?
Lastly if I have 2 servers configured identically (one working as a
production server and the other as a backup server) and a problem arises wit
h
the production server can I simply just switch IP's and have the backup
server quickly become the production? Is this a standard practice Or will I
have to preform more adjustments?
Thanks
DreSELECT @.@.Servername (<InstanceName> for default,
Servername\<InstanceName> for named ones)
"Secondly how do I adjust a named instance to be the default instance?"
AFAIK thats not possible, you can only deinstall and reinstall
everything cause even the Windows services have to be rebuilt from the
setup.
HTH, jens Suessmeyer-|||Two servers cannot have same name, so you to name them different with
different IP addresses. When the production server fails you have to
update your internal DNS for production server to point backup server.sql
Default instance VS Named instance
If you have a choice to pick default instance or named instance, which one
will you choose and why ?
One saying is named instance provides more descriptions
to the DBAs if they need to managed many DBs.Hi
Having multiple instances on a single machine will use up additional
resources, but there are valid reasons to do so, including ones related to
secutity an access. Having a single named instance on a machine, is probably
a personal preference, although you will always need to know and specify the
instance name when connecting to it.
I seem to remember that MSDE will only install as a named instance, but can
find where I saw it!
John
"Angus" wrote:
> If you have a choice to pick default instance or named instance, which one
> will you choose and why ?
> One saying is named instance provides more descriptions
> to the DBAs if they need to managed many DBs.|||MSDE can run under and be installed under either. The problem is that it
typically is installed where another instance is already running.
Some applications can not connect to a named instance, the "\" in the server
name throws them off for some reason.
Other than that, it makes no difference. If you are running multiple
instances, you have to have a way to distinguish them and their respectie
binaries and services, thus the concept of a named instance to begin with.
Sincerely,
Anthony Thomas
"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:EF5564B6-0087-408C-9DE4-B9792CF7BB31@.microsoft.com...
Hi
Having multiple instances on a single machine will use up additional
resources, but there are valid reasons to do so, including ones related to
secutity an access. Having a single named instance on a machine, is probably
a personal preference, although you will always need to know and specify the
instance name when connecting to it.
I seem to remember that MSDE will only install as a named instance, but can
find where I saw it!
John
"Angus" wrote:
> If you have a choice to pick default instance or named instance, which one
> will you choose and why ?
> One saying is named instance provides more descriptions
> to the DBAs if they need to managed many DBs.
will you choose and why ?
One saying is named instance provides more descriptions
to the DBAs if they need to managed many DBs.Hi
Having multiple instances on a single machine will use up additional
resources, but there are valid reasons to do so, including ones related to
secutity an access. Having a single named instance on a machine, is probably
a personal preference, although you will always need to know and specify the
instance name when connecting to it.
I seem to remember that MSDE will only install as a named instance, but can
find where I saw it!
John
"Angus" wrote:
> If you have a choice to pick default instance or named instance, which one
> will you choose and why ?
> One saying is named instance provides more descriptions
> to the DBAs if they need to managed many DBs.|||MSDE can run under and be installed under either. The problem is that it
typically is installed where another instance is already running.
Some applications can not connect to a named instance, the "\" in the server
name throws them off for some reason.
Other than that, it makes no difference. If you are running multiple
instances, you have to have a way to distinguish them and their respectie
binaries and services, thus the concept of a named instance to begin with.
Sincerely,
Anthony Thomas
"John Bell" <JohnBell@.discussions.microsoft.com> wrote in message
news:EF5564B6-0087-408C-9DE4-B9792CF7BB31@.microsoft.com...
Hi
Having multiple instances on a single machine will use up additional
resources, but there are valid reasons to do so, including ones related to
secutity an access. Having a single named instance on a machine, is probably
a personal preference, although you will always need to know and specify the
instance name when connecting to it.
I seem to remember that MSDE will only install as a named instance, but can
find where I saw it!
John
"Angus" wrote:
> If you have a choice to pick default instance or named instance, which one
> will you choose and why ?
> One saying is named instance provides more descriptions
> to the DBAs if they need to managed many DBs.
Default Instance Named MSSQLSERVER
Does anyone know why, when I install SQL Server 2005 Developer (September
CTP) and select Default Instance during setup that I see the following in th
e
SQL Server 2005 Services area of SQL Server Configuration Manager.
SQL Server Agent (MSSQLSERVER)
SQL Server (MSSQLSERVER)
SQL Server Analysis Server (MSSQLSERVER)
SQL Server Reporting Services (MSSQLSERVER)
The physical box name is DEVDW but it seems the default instance is named
MSSQLServer which I definitely did not specifiy...I'm very confused.That is the service name, and it hasn't changes since version 6.0.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:01D3B95C-611D-4EC3-BF67-C5D8D5C46A75@.microsoft.com...
> Does anyone know why, when I install SQL Server 2005 Developer (September
> CTP) and select Default Instance during setup that I see the following in
the
> SQL Server 2005 Services area of SQL Server Configuration Manager.
> SQL Server Agent (MSSQLSERVER)
> SQL Server (MSSQLSERVER)
> SQL Server Analysis Server (MSSQLSERVER)
> SQL Server Reporting Services (MSSQLSERVER)
> The physical box name is DEVDW but it seems the default instance is named
> MSSQLServer which I definitely did not specifiy...I'm very confused.
>|||So you're saying that SQL Server Agent, SQL Server Analysis Services and SQL
Server Reporting Services are all running under the MSSQLServer Service...I
don't think so. This is the "name" of the instance and I'm not sure why.
"Scott" wrote:
> Does anyone know why, when I install SQL Server 2005 Developer (September
> CTP) and select Default Instance during setup that I see the following in
the
> SQL Server 2005 Services area of SQL Server Configuration Manager.
> SQL Server Agent (MSSQLSERVER)
> SQL Server (MSSQLSERVER)
> SQL Server Analysis Server (MSSQLSERVER)
> SQL Server Reporting Services (MSSQLSERVER)
> The physical box name is DEVDW but it seems the default instance is named
> MSSQLServer which I definitely did not specifiy...I'm very confused.
>|||"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:4403E7F6-9F4C-4B51-B0D0-9B950725D36E@.microsoft.com...
> So you're saying that SQL Server Agent, SQL Server Analysis Services and
> SQL
> Server Reporting Services are all running under the MSSQLServer
> Service...I
> don't think so. This is the "name" of the instance and I'm not sure why.
>
This is the "name" of the default instance. If you installed a named
instance of SQL Server you would see the instance name instead. It's really
just there so you can identify all the services related to that instance.
David
CTP) and select Default Instance during setup that I see the following in th
e
SQL Server 2005 Services area of SQL Server Configuration Manager.
SQL Server Agent (MSSQLSERVER)
SQL Server (MSSQLSERVER)
SQL Server Analysis Server (MSSQLSERVER)
SQL Server Reporting Services (MSSQLSERVER)
The physical box name is DEVDW but it seems the default instance is named
MSSQLServer which I definitely did not specifiy...I'm very confused.That is the service name, and it hasn't changes since version 6.0.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:01D3B95C-611D-4EC3-BF67-C5D8D5C46A75@.microsoft.com...
> Does anyone know why, when I install SQL Server 2005 Developer (September
> CTP) and select Default Instance during setup that I see the following in
the
> SQL Server 2005 Services area of SQL Server Configuration Manager.
> SQL Server Agent (MSSQLSERVER)
> SQL Server (MSSQLSERVER)
> SQL Server Analysis Server (MSSQLSERVER)
> SQL Server Reporting Services (MSSQLSERVER)
> The physical box name is DEVDW but it seems the default instance is named
> MSSQLServer which I definitely did not specifiy...I'm very confused.
>|||So you're saying that SQL Server Agent, SQL Server Analysis Services and SQL
Server Reporting Services are all running under the MSSQLServer Service...I
don't think so. This is the "name" of the instance and I'm not sure why.
"Scott" wrote:
> Does anyone know why, when I install SQL Server 2005 Developer (September
> CTP) and select Default Instance during setup that I see the following in
the
> SQL Server 2005 Services area of SQL Server Configuration Manager.
> SQL Server Agent (MSSQLSERVER)
> SQL Server (MSSQLSERVER)
> SQL Server Analysis Server (MSSQLSERVER)
> SQL Server Reporting Services (MSSQLSERVER)
> The physical box name is DEVDW but it seems the default instance is named
> MSSQLServer which I definitely did not specifiy...I'm very confused.
>|||"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:4403E7F6-9F4C-4B51-B0D0-9B950725D36E@.microsoft.com...
> So you're saying that SQL Server Agent, SQL Server Analysis Services and
> SQL
> Server Reporting Services are all running under the MSSQLServer
> Service...I
> don't think so. This is the "name" of the instance and I'm not sure why.
>
This is the "name" of the default instance. If you installed a named
instance of SQL Server you would see the instance name instead. It's really
just there so you can identify all the services related to that instance.
David
Default Instance Named MSSQLSERVER
Does anyone know why, when I install SQL Server 2005 Developer (September
CTP) and select Default Instance during setup that I see the following in the
SQL Server 2005 Services area of SQL Server Configuration Manager.
SQL Server Agent (MSSQLSERVER)
SQL Server (MSSQLSERVER)
SQL Server Analysis Server (MSSQLSERVER)
SQL Server Reporting Services (MSSQLSERVER)
The physical box name is DEVDW but it seems the default instance is named
MSSQLServer which I definitely did not specifiy...I'm very confused.
That is the service name, and it hasn't changes since version 6.0.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:01D3B95C-611D-4EC3-BF67-C5D8D5C46A75@.microsoft.com...
> Does anyone know why, when I install SQL Server 2005 Developer (September
> CTP) and select Default Instance during setup that I see the following in the
> SQL Server 2005 Services area of SQL Server Configuration Manager.
> SQL Server Agent (MSSQLSERVER)
> SQL Server (MSSQLSERVER)
> SQL Server Analysis Server (MSSQLSERVER)
> SQL Server Reporting Services (MSSQLSERVER)
> The physical box name is DEVDW but it seems the default instance is named
> MSSQLServer which I definitely did not specifiy...I'm very confused.
>
|||So you're saying that SQL Server Agent, SQL Server Analysis Services and SQL
Server Reporting Services are all running under the MSSQLServer Service...I
don't think so. This is the "name" of the instance and I'm not sure why.
"Scott" wrote:
> Does anyone know why, when I install SQL Server 2005 Developer (September
> CTP) and select Default Instance during setup that I see the following in the
> SQL Server 2005 Services area of SQL Server Configuration Manager.
> SQL Server Agent (MSSQLSERVER)
> SQL Server (MSSQLSERVER)
> SQL Server Analysis Server (MSSQLSERVER)
> SQL Server Reporting Services (MSSQLSERVER)
> The physical box name is DEVDW but it seems the default instance is named
> MSSQLServer which I definitely did not specifiy...I'm very confused.
>
|||"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:4403E7F6-9F4C-4B51-B0D0-9B950725D36E@.microsoft.com...
> So you're saying that SQL Server Agent, SQL Server Analysis Services and
> SQL
> Server Reporting Services are all running under the MSSQLServer
> Service...I
> don't think so. This is the "name" of the instance and I'm not sure why.
>
This is the "name" of the default instance. If you installed a named
instance of SQL Server you would see the instance name instead. It's really
just there so you can identify all the services related to that instance.
David
CTP) and select Default Instance during setup that I see the following in the
SQL Server 2005 Services area of SQL Server Configuration Manager.
SQL Server Agent (MSSQLSERVER)
SQL Server (MSSQLSERVER)
SQL Server Analysis Server (MSSQLSERVER)
SQL Server Reporting Services (MSSQLSERVER)
The physical box name is DEVDW but it seems the default instance is named
MSSQLServer which I definitely did not specifiy...I'm very confused.
That is the service name, and it hasn't changes since version 6.0.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:01D3B95C-611D-4EC3-BF67-C5D8D5C46A75@.microsoft.com...
> Does anyone know why, when I install SQL Server 2005 Developer (September
> CTP) and select Default Instance during setup that I see the following in the
> SQL Server 2005 Services area of SQL Server Configuration Manager.
> SQL Server Agent (MSSQLSERVER)
> SQL Server (MSSQLSERVER)
> SQL Server Analysis Server (MSSQLSERVER)
> SQL Server Reporting Services (MSSQLSERVER)
> The physical box name is DEVDW but it seems the default instance is named
> MSSQLServer which I definitely did not specifiy...I'm very confused.
>
|||So you're saying that SQL Server Agent, SQL Server Analysis Services and SQL
Server Reporting Services are all running under the MSSQLServer Service...I
don't think so. This is the "name" of the instance and I'm not sure why.
"Scott" wrote:
> Does anyone know why, when I install SQL Server 2005 Developer (September
> CTP) and select Default Instance during setup that I see the following in the
> SQL Server 2005 Services area of SQL Server Configuration Manager.
> SQL Server Agent (MSSQLSERVER)
> SQL Server (MSSQLSERVER)
> SQL Server Analysis Server (MSSQLSERVER)
> SQL Server Reporting Services (MSSQLSERVER)
> The physical box name is DEVDW but it seems the default instance is named
> MSSQLServer which I definitely did not specifiy...I'm very confused.
>
|||"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:4403E7F6-9F4C-4B51-B0D0-9B950725D36E@.microsoft.com...
> So you're saying that SQL Server Agent, SQL Server Analysis Services and
> SQL
> Server Reporting Services are all running under the MSSQLServer
> Service...I
> don't think so. This is the "name" of the instance and I'm not sure why.
>
This is the "name" of the default instance. If you installed a named
instance of SQL Server you would see the instance name instead. It's really
just there so you can identify all the services related to that instance.
David
Default Instance Named MSSQLSERVER
Does anyone know why, when I install SQL Server 2005 Developer (September
CTP) and select Default Instance during setup that I see the following in the
SQL Server 2005 Services area of SQL Server Configuration Manager.
SQL Server Agent (MSSQLSERVER)
SQL Server (MSSQLSERVER)
SQL Server Analysis Server (MSSQLSERVER)
SQL Server Reporting Services (MSSQLSERVER)
The physical box name is DEVDW but it seems the default instance is named
MSSQLServer which I definitely did not specifiy...I'm very confused.That is the service name, and it hasn't changes since version 6.0.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:01D3B95C-611D-4EC3-BF67-C5D8D5C46A75@.microsoft.com...
> Does anyone know why, when I install SQL Server 2005 Developer (September
> CTP) and select Default Instance during setup that I see the following in the
> SQL Server 2005 Services area of SQL Server Configuration Manager.
> SQL Server Agent (MSSQLSERVER)
> SQL Server (MSSQLSERVER)
> SQL Server Analysis Server (MSSQLSERVER)
> SQL Server Reporting Services (MSSQLSERVER)
> The physical box name is DEVDW but it seems the default instance is named
> MSSQLServer which I definitely did not specifiy...I'm very confused.
>|||So you're saying that SQL Server Agent, SQL Server Analysis Services and SQL
Server Reporting Services are all running under the MSSQLServer Service...I
don't think so. This is the "name" of the instance and I'm not sure why.
"Scott" wrote:
> Does anyone know why, when I install SQL Server 2005 Developer (September
> CTP) and select Default Instance during setup that I see the following in the
> SQL Server 2005 Services area of SQL Server Configuration Manager.
> SQL Server Agent (MSSQLSERVER)
> SQL Server (MSSQLSERVER)
> SQL Server Analysis Server (MSSQLSERVER)
> SQL Server Reporting Services (MSSQLSERVER)
> The physical box name is DEVDW but it seems the default instance is named
> MSSQLServer which I definitely did not specifiy...I'm very confused.
>|||"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:4403E7F6-9F4C-4B51-B0D0-9B950725D36E@.microsoft.com...
> So you're saying that SQL Server Agent, SQL Server Analysis Services and
> SQL
> Server Reporting Services are all running under the MSSQLServer
> Service...I
> don't think so. This is the "name" of the instance and I'm not sure why.
>
This is the "name" of the default instance. If you installed a named
instance of SQL Server you would see the instance name instead. It's really
just there so you can identify all the services related to that instance.
David
CTP) and select Default Instance during setup that I see the following in the
SQL Server 2005 Services area of SQL Server Configuration Manager.
SQL Server Agent (MSSQLSERVER)
SQL Server (MSSQLSERVER)
SQL Server Analysis Server (MSSQLSERVER)
SQL Server Reporting Services (MSSQLSERVER)
The physical box name is DEVDW but it seems the default instance is named
MSSQLServer which I definitely did not specifiy...I'm very confused.That is the service name, and it hasn't changes since version 6.0.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:01D3B95C-611D-4EC3-BF67-C5D8D5C46A75@.microsoft.com...
> Does anyone know why, when I install SQL Server 2005 Developer (September
> CTP) and select Default Instance during setup that I see the following in the
> SQL Server 2005 Services area of SQL Server Configuration Manager.
> SQL Server Agent (MSSQLSERVER)
> SQL Server (MSSQLSERVER)
> SQL Server Analysis Server (MSSQLSERVER)
> SQL Server Reporting Services (MSSQLSERVER)
> The physical box name is DEVDW but it seems the default instance is named
> MSSQLServer which I definitely did not specifiy...I'm very confused.
>|||So you're saying that SQL Server Agent, SQL Server Analysis Services and SQL
Server Reporting Services are all running under the MSSQLServer Service...I
don't think so. This is the "name" of the instance and I'm not sure why.
"Scott" wrote:
> Does anyone know why, when I install SQL Server 2005 Developer (September
> CTP) and select Default Instance during setup that I see the following in the
> SQL Server 2005 Services area of SQL Server Configuration Manager.
> SQL Server Agent (MSSQLSERVER)
> SQL Server (MSSQLSERVER)
> SQL Server Analysis Server (MSSQLSERVER)
> SQL Server Reporting Services (MSSQLSERVER)
> The physical box name is DEVDW but it seems the default instance is named
> MSSQLServer which I definitely did not specifiy...I'm very confused.
>|||"Scott" <Scott@.discussions.microsoft.com> wrote in message
news:4403E7F6-9F4C-4B51-B0D0-9B950725D36E@.microsoft.com...
> So you're saying that SQL Server Agent, SQL Server Analysis Services and
> SQL
> Server Reporting Services are all running under the MSSQLServer
> Service...I
> don't think so. This is the "name" of the instance and I'm not sure why.
>
This is the "name" of the default instance. If you installed a named
instance of SQL Server you would see the instance name instead. It's really
just there so you can identify all the services related to that instance.
David
DEFAULT INSTANCE INSTALLATION PROBLEM ON SQL2005
I have win2003 machine which is named fenermarket.
I have an installed instance which is FENERMARKET\ALISVERISSAATI.
I installed sp1 and sp2 too.
When i try to install default instance as another instance the setup process
give the error.Im sure that my Sa password is true. I choose windows
authentication as aut type.
SQL service MSSQLSERVER started successfully waiting for SQL service to
accept client connections
Service MSSQLSERVER started at Mon Feb 04 19:18:21 2008
Loaded DLL:
C:\WINDOWS\system32\Odbc32.dll
Version:
3.526.3959.0
SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=28000, level=-1, state=-1, native_error=18456, msg=[Microsoft][SQL
Native Client][SQL Server]Login failed for user 'sa'.
Error Code: 0x80074818 (18456)
Windows Error Text: Source File Name: lib\odbc_connection.cpp
Compiler Timestamp: Fri Jul 29 01:13:53 2005
Function Name: OdbcConnection::connect@.connect
Source Line Number: 148
-- Context ---
Connecting to SQL Server
ExecuteSqlCommands
Originial error was 80074818 (18456)
ipt
SqlScriptHlpr
Error Code: 18456
Where do you need the "sa" Login and it's password if you use Windows
Authentication in SQL Server Setup?
In this error, the key thing is to see the "State number" in Login Failed
error message. Here is a nice blog about this error:
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
Ekrem nsoy
"in da club" <s> wrote in message
news:umNJdQ1ZIHA.1164@.TK2MSFTNGP02.phx.gbl...
>I have win2003 machine which is named fenermarket.
> I have an installed instance which is FENERMARKET\ALISVERISSAATI.
> I installed sp1 and sp2 too.
> When i try to install default instance as another instance the setup
> process give the error.Im sure that my Sa password is true. I choose
> windows authentication as aut type.
>
> SQL service MSSQLSERVER started successfully waiting for SQL service to
> accept client connections
> Service MSSQLSERVER started at Mon Feb 04 19:18:21 2008
> Loaded DLL:
> C:\WINDOWS\system32\Odbc32.dll
> Version:
> 3.526.3959.0
>
> SQL_ERROR (-1) in OdbcConnection::connect
> sqlstate=28000, level=-1, state=-1, native_error=18456,
> msg=[Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'.
> Error Code: 0x80074818 (18456)
> Windows Error Text: Source File Name: lib\odbc_connection.cpp
> Compiler Timestamp: Fri Jul 29 01:13:53 2005
> Function Name: OdbcConnection::connect@.connect
> Source Line Number: 148
>
> -- Context ---
>
> Connecting to SQL Server
> ExecuteSqlCommands
> Originial error was 80074818 (18456)
> ipt
> SqlScriptHlpr
>
> Error Code: 18456
>
|||i have choosen mixed mode. I know the url but i couldnt find any info about
my stuation . my error state id is not listed here.
sql
I have an installed instance which is FENERMARKET\ALISVERISSAATI.
I installed sp1 and sp2 too.
When i try to install default instance as another instance the setup process
give the error.Im sure that my Sa password is true. I choose windows
authentication as aut type.
SQL service MSSQLSERVER started successfully waiting for SQL service to
accept client connections
Service MSSQLSERVER started at Mon Feb 04 19:18:21 2008
Loaded DLL:
C:\WINDOWS\system32\Odbc32.dll
Version:
3.526.3959.0
SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=28000, level=-1, state=-1, native_error=18456, msg=[Microsoft][SQL
Native Client][SQL Server]Login failed for user 'sa'.
Error Code: 0x80074818 (18456)
Windows Error Text: Source File Name: lib\odbc_connection.cpp
Compiler Timestamp: Fri Jul 29 01:13:53 2005
Function Name: OdbcConnection::connect@.connect
Source Line Number: 148
-- Context ---
Connecting to SQL Server
ExecuteSqlCommands
Originial error was 80074818 (18456)
ipt
SqlScriptHlpr
Error Code: 18456
Where do you need the "sa" Login and it's password if you use Windows
Authentication in SQL Server Setup?
In this error, the key thing is to see the "State number" in Login Failed
error message. Here is a nice blog about this error:
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
Ekrem nsoy
"in da club" <s> wrote in message
news:umNJdQ1ZIHA.1164@.TK2MSFTNGP02.phx.gbl...
>I have win2003 machine which is named fenermarket.
> I have an installed instance which is FENERMARKET\ALISVERISSAATI.
> I installed sp1 and sp2 too.
> When i try to install default instance as another instance the setup
> process give the error.Im sure that my Sa password is true. I choose
> windows authentication as aut type.
>
> SQL service MSSQLSERVER started successfully waiting for SQL service to
> accept client connections
> Service MSSQLSERVER started at Mon Feb 04 19:18:21 2008
> Loaded DLL:
> C:\WINDOWS\system32\Odbc32.dll
> Version:
> 3.526.3959.0
>
> SQL_ERROR (-1) in OdbcConnection::connect
> sqlstate=28000, level=-1, state=-1, native_error=18456,
> msg=[Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'.
> Error Code: 0x80074818 (18456)
> Windows Error Text: Source File Name: lib\odbc_connection.cpp
> Compiler Timestamp: Fri Jul 29 01:13:53 2005
> Function Name: OdbcConnection::connect@.connect
> Source Line Number: 148
>
> -- Context ---
>
> Connecting to SQL Server
> ExecuteSqlCommands
> Originial error was 80074818 (18456)
> ipt
> SqlScriptHlpr
>
> Error Code: 18456
>
|||i have choosen mixed mode. I know the url but i couldnt find any info about
my stuation . my error state id is not listed here.
sql
DEFAULT INSTANCE INSTALLATION PROBLEM ON SQL2005
I have win2003 machine which is named fenermarket.
I have an installed instance which is FENERMARKET\ALISVERISSAATI.
I installed sp1 and sp2 too.
When i try to install default instance as another instance the setup process
give the error.Im sure that my Sa password is true. I choose windows
authentication as aut type.
SQL service MSSQLSERVER started successfully waiting for SQL service to
accept client connections
Service MSSQLSERVER started at Mon Feb 04 19:18:21 2008
Loaded DLL:
C:\WINDOWS\system32\Odbc32.dll
Version:
3.526.3959.0
SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=28000, level=-1, state=-1, native_error=18456, msg=[Microsoft][SQL
Native Client][SQL Server]Login failed for user 'sa'.
Error Code: 0x80074818 (18456)
Windows Error Text: Source File Name: lib\odbc_connection.cpp
Compiler Timestamp: Fri Jul 29 01:13:53 2005
Function Name: OdbcConnection::connect@.connect
Source Line Number: 148
-- Context ---
Connecting to SQL Server
ExecuteSqlCommands
Originial error was 80074818 (18456)
ipt
SqlScriptHlpr
Error Code: 18456Where do you need the "sa" Login and it's password if you use Windows
Authentication in SQL Server Setup?
In this error, the key thing is to see the "State number" in Login Failed
error message. Here is a nice blog about this error:
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
--
Ekrem Önsoy
"in da club" <s> wrote in message
news:umNJdQ1ZIHA.1164@.TK2MSFTNGP02.phx.gbl...
>I have win2003 machine which is named fenermarket.
> I have an installed instance which is FENERMARKET\ALISVERISSAATI.
> I installed sp1 and sp2 too.
> When i try to install default instance as another instance the setup
> process give the error.Im sure that my Sa password is true. I choose
> windows authentication as aut type.
>
> SQL service MSSQLSERVER started successfully waiting for SQL service to
> accept client connections
> Service MSSQLSERVER started at Mon Feb 04 19:18:21 2008
> Loaded DLL:
> C:\WINDOWS\system32\Odbc32.dll
> Version:
> 3.526.3959.0
>
> SQL_ERROR (-1) in OdbcConnection::connect
> sqlstate=28000, level=-1, state=-1, native_error=18456,
> msg=[Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'.
> Error Code: 0x80074818 (18456)
> Windows Error Text: Source File Name: lib\odbc_connection.cpp
> Compiler Timestamp: Fri Jul 29 01:13:53 2005
> Function Name: OdbcConnection::connect@.connect
> Source Line Number: 148
>
> -- Context ---
>
> Connecting to SQL Server
> ExecuteSqlCommands
> Originial error was 80074818 (18456)
> ipt
> SqlScriptHlpr
>
> Error Code: 18456
>|||i have choosen mixed mode. I know the url but i couldnt find any info about
my stuation . my error state id is not listed here.
I have an installed instance which is FENERMARKET\ALISVERISSAATI.
I installed sp1 and sp2 too.
When i try to install default instance as another instance the setup process
give the error.Im sure that my Sa password is true. I choose windows
authentication as aut type.
SQL service MSSQLSERVER started successfully waiting for SQL service to
accept client connections
Service MSSQLSERVER started at Mon Feb 04 19:18:21 2008
Loaded DLL:
C:\WINDOWS\system32\Odbc32.dll
Version:
3.526.3959.0
SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=28000, level=-1, state=-1, native_error=18456, msg=[Microsoft][SQL
Native Client][SQL Server]Login failed for user 'sa'.
Error Code: 0x80074818 (18456)
Windows Error Text: Source File Name: lib\odbc_connection.cpp
Compiler Timestamp: Fri Jul 29 01:13:53 2005
Function Name: OdbcConnection::connect@.connect
Source Line Number: 148
-- Context ---
Connecting to SQL Server
ExecuteSqlCommands
Originial error was 80074818 (18456)
ipt
SqlScriptHlpr
Error Code: 18456Where do you need the "sa" Login and it's password if you use Windows
Authentication in SQL Server Setup?
In this error, the key thing is to see the "State number" in Login Failed
error message. Here is a nice blog about this error:
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
--
Ekrem Önsoy
"in da club" <s> wrote in message
news:umNJdQ1ZIHA.1164@.TK2MSFTNGP02.phx.gbl...
>I have win2003 machine which is named fenermarket.
> I have an installed instance which is FENERMARKET\ALISVERISSAATI.
> I installed sp1 and sp2 too.
> When i try to install default instance as another instance the setup
> process give the error.Im sure that my Sa password is true. I choose
> windows authentication as aut type.
>
> SQL service MSSQLSERVER started successfully waiting for SQL service to
> accept client connections
> Service MSSQLSERVER started at Mon Feb 04 19:18:21 2008
> Loaded DLL:
> C:\WINDOWS\system32\Odbc32.dll
> Version:
> 3.526.3959.0
>
> SQL_ERROR (-1) in OdbcConnection::connect
> sqlstate=28000, level=-1, state=-1, native_error=18456,
> msg=[Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'.
> Error Code: 0x80074818 (18456)
> Windows Error Text: Source File Name: lib\odbc_connection.cpp
> Compiler Timestamp: Fri Jul 29 01:13:53 2005
> Function Name: OdbcConnection::connect@.connect
> Source Line Number: 148
>
> -- Context ---
>
> Connecting to SQL Server
> ExecuteSqlCommands
> Originial error was 80074818 (18456)
> ipt
> SqlScriptHlpr
>
> Error Code: 18456
>|||i have choosen mixed mode. I know the url but i couldnt find any info about
my stuation . my error state id is not listed here.
Default Instance
I have two instances running one is on SqlServer 7 and second one is on
SqlServer 2000 (default). I want to make the default instance to SqlServer 7
, how can I ?
Thanks
Noor
hi Noor,
"Noor" <noor@.ngsol.com> ha scritto nel messaggio
news:OELbeuZaEHA.972@.TK2MSFTNGP12.phx.gbl...
> I have two instances running one is on SqlServer 7 and second one is on
> SqlServer 2000 (default). I want to make the default instance to SqlServer
7
> , how can I ?
AFAIK, in a scenario where both a SQL Server 7.0 and a SQL Server 2000 are
installed on the same computer, only the SQL Server 7.0 can be the default
instance, as SQL Server 7.0 has not been designed to support named
instance...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Okie now let's assume I have two instances running one is on SqlServer
2000 - SQL1 and second one is on
SqlServer 2000 - SQL2 (default). I want to make the default instance to
SQL1.
how can I ?
Thanks
NOOR
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2lkvfdFe02fhU1@.uni-berlin.de...[vbcol=seagreen]
> hi Noor,
> "Noor" <noor@.ngsol.com> ha scritto nel messaggio
> news:OELbeuZaEHA.972@.TK2MSFTNGP12.phx.gbl...
SqlServer
> 7
> AFAIK, in a scenario where both a SQL Server 7.0 and a SQL Server 2000 are
> installed on the same computer, only the SQL Server 7.0 can be the default
> instance, as SQL Server 7.0 has not been designed to support named
> instance...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Hi,
You cant change the Named Instance of SQL Server to a Default instance. The
only solution is to reinstall
the SQL Server both instances.
Thanks
Hari
MCDBA
"Noor" <noor@.ngsol.com> wrote in message
news:#XQtMSiaEHA.1656@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Okie now let's assume I have two instances running one is on SqlServer
> 2000 - SQL1 and second one is on
> SqlServer 2000 - SQL2 (default). I want to make the default instance to
> SQL1.
> how can I ?
> Thanks
> NOOR
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:2lkvfdFe02fhU1@.uni-berlin.de...
on[vbcol=seagreen]
> SqlServer
are[vbcol=seagreen]
default
>
|||Right Thanks, Let's assume I already have Default Instance running on my
system and now I am going to install new Instance and at the run time I
wanna set it as a default Instance so Can I do this or I have to remove the
Default Instance first ?
Thanks
Noor
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:uFmbaejaEHA.3596@.tk2msftngp13.phx.gbl...
> Hi,
> You cant change the Named Instance of SQL Server to a Default instance.
The[vbcol=seagreen]
> only solution is to reinstall
> the SQL Server both instances.
>
> --
> Thanks
> Hari
> MCDBA
> "Noor" <noor@.ngsol.com> wrote in message
> news:#XQtMSiaEHA.1656@.TK2MSFTNGP09.phx.gbl...
> on
> are
> default
visual
>
|||Hi,
No, you cant do that. If you have a default instance already running then
you can only install a named instance. I feel that "default " check box will
be disabled.
Thanks
Hari
MCDBA
"Noor" <noor@.ngsol.com> wrote in message
news:u9JQQkjaEHA.1248@.TK2MSFTNGP11.phx.gbl...
> Right Thanks, Let's assume I already have Default Instance running on my
> system and now I am going to install new Instance and at the run time I
> wanna set it as a default Instance so Can I do this or I have to remove
the[vbcol=seagreen]
> Default Instance first ?
> Thanks
> Noor
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:uFmbaejaEHA.3596@.tk2msftngp13.phx.gbl...
> The
to[vbcol=seagreen]
is[vbcol=seagreen]
2000
> visual
>
|||but you could fool network clients into thinking it was the default instance
by changing the network listening endpoints (i.e. stop your default instance
and have your named instance listen on tcp port 1433, for example), and have
clients connect up to "servername,1433".
It's a hack but it might work for what you want to do.
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:O4llMrkaEHA.2812@.tk2msftngp13.phx.gbl...
> Hi,
> No, you cant do that. If you have a default instance already running then
> you can only install a named instance. I feel that "default " check box
> will
> be disabled.
> --
> Thanks
> Hari
> MCDBA
> "Noor" <noor@.ngsol.com> wrote in message
> news:u9JQQkjaEHA.1248@.TK2MSFTNGP11.phx.gbl...
> the
> to
> is
> 2000
>
SqlServer 2000 (default). I want to make the default instance to SqlServer 7
, how can I ?
Thanks
Noor
hi Noor,
"Noor" <noor@.ngsol.com> ha scritto nel messaggio
news:OELbeuZaEHA.972@.TK2MSFTNGP12.phx.gbl...
> I have two instances running one is on SqlServer 7 and second one is on
> SqlServer 2000 (default). I want to make the default instance to SqlServer
7
> , how can I ?
AFAIK, in a scenario where both a SQL Server 7.0 and a SQL Server 2000 are
installed on the same computer, only the SQL Server 7.0 can be the default
instance, as SQL Server 7.0 has not been designed to support named
instance...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Okie now let's assume I have two instances running one is on SqlServer
2000 - SQL1 and second one is on
SqlServer 2000 - SQL2 (default). I want to make the default instance to
SQL1.
how can I ?
Thanks
NOOR
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2lkvfdFe02fhU1@.uni-berlin.de...[vbcol=seagreen]
> hi Noor,
> "Noor" <noor@.ngsol.com> ha scritto nel messaggio
> news:OELbeuZaEHA.972@.TK2MSFTNGP12.phx.gbl...
SqlServer
> 7
> AFAIK, in a scenario where both a SQL Server 7.0 and a SQL Server 2000 are
> installed on the same computer, only the SQL Server 7.0 can be the default
> instance, as SQL Server 7.0 has not been designed to support named
> instance...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Hi,
You cant change the Named Instance of SQL Server to a Default instance. The
only solution is to reinstall
the SQL Server both instances.
Thanks
Hari
MCDBA
"Noor" <noor@.ngsol.com> wrote in message
news:#XQtMSiaEHA.1656@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Okie now let's assume I have two instances running one is on SqlServer
> 2000 - SQL1 and second one is on
> SqlServer 2000 - SQL2 (default). I want to make the default instance to
> SQL1.
> how can I ?
> Thanks
> NOOR
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:2lkvfdFe02fhU1@.uni-berlin.de...
on[vbcol=seagreen]
> SqlServer
are[vbcol=seagreen]
default
>
|||Right Thanks, Let's assume I already have Default Instance running on my
system and now I am going to install new Instance and at the run time I
wanna set it as a default Instance so Can I do this or I have to remove the
Default Instance first ?
Thanks
Noor
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:uFmbaejaEHA.3596@.tk2msftngp13.phx.gbl...
> Hi,
> You cant change the Named Instance of SQL Server to a Default instance.
The[vbcol=seagreen]
> only solution is to reinstall
> the SQL Server both instances.
>
> --
> Thanks
> Hari
> MCDBA
> "Noor" <noor@.ngsol.com> wrote in message
> news:#XQtMSiaEHA.1656@.TK2MSFTNGP09.phx.gbl...
> on
> are
> default
visual
>
|||Hi,
No, you cant do that. If you have a default instance already running then
you can only install a named instance. I feel that "default " check box will
be disabled.
Thanks
Hari
MCDBA
"Noor" <noor@.ngsol.com> wrote in message
news:u9JQQkjaEHA.1248@.TK2MSFTNGP11.phx.gbl...
> Right Thanks, Let's assume I already have Default Instance running on my
> system and now I am going to install new Instance and at the run time I
> wanna set it as a default Instance so Can I do this or I have to remove
the[vbcol=seagreen]
> Default Instance first ?
> Thanks
> Noor
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:uFmbaejaEHA.3596@.tk2msftngp13.phx.gbl...
> The
to[vbcol=seagreen]
is[vbcol=seagreen]
2000
> visual
>
|||but you could fool network clients into thinking it was the default instance
by changing the network listening endpoints (i.e. stop your default instance
and have your named instance listen on tcp port 1433, for example), and have
clients connect up to "servername,1433".
It's a hack but it might work for what you want to do.
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:O4llMrkaEHA.2812@.tk2msftngp13.phx.gbl...
> Hi,
> No, you cant do that. If you have a default instance already running then
> you can only install a named instance. I feel that "default " check box
> will
> be disabled.
> --
> Thanks
> Hari
> MCDBA
> "Noor" <noor@.ngsol.com> wrote in message
> news:u9JQQkjaEHA.1248@.TK2MSFTNGP11.phx.gbl...
> the
> to
> is
> 2000
>
Tuesday, March 27, 2012
Default Instance
Our installation of SQL server 2000 has been installed as
a named instance, and I am trying to install SMS2003. I
have read in the documentation that SMS2003 cannot be run
on a named instance, and must be run on the default
instance.
Is there any way of switching the named instance to the
default instance, or does anyone have any ideas on how I
can overcome this problem without reinstalling SQL server?
Hi,
As far as I know, You need to reinstall SQL server to move from named to
default instance.
Thanks
Hari
MCDBA
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
> Our installation of SQL server 2000 has been installed as
> a named instance, and I am trying to install SMS2003. I
> have read in the documentation that SMS2003 cannot be run
> on a named instance, and must be run on the default
> instance.
> Is there any way of switching the named instance to the
> default instance, or does anyone have any ideas on how I
> can overcome this problem without reinstalling SQL server?
|||You will have to re-install SQL... But you can get your databases back by
backup/restore or sp_detach_db sp_attach_db
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
> Our installation of SQL server 2000 has been installed as
> a named instance, and I am trying to install SMS2003. I
> have read in the documentation that SMS2003 cannot be run
> on a named instance, and must be run on the default
> instance.
> Is there any way of switching the named instance to the
> default instance, or does anyone have any ideas on how I
> can overcome this problem without reinstalling SQL server?
|||Will this restore the security, or will I have to restore
the Master DB as well?
>--Original Message--
>You will have to re-install SQL... But you can get your
databases back by
>backup/restore or sp_detach_db sp_attach_db
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Mariner, Charlotte, NC
>www.mariner-usa.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"chris" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
as[vbcol=seagreen]
I[vbcol=seagreen]
run[vbcol=seagreen]
I[vbcol=seagreen]
server?
>
>.
>
|||Hi,
To restore the SQl Server Logins you have to restore the Master database as
well. This will ensure that your security chain is brought back as same as
old.
Master database can be restored only if you start sql server in single user
mode.
How to start SQl server in single user mode:-
Execute the below command from command prompt
sqlservr.exe -c -m
Thanks
Hari
MCDBA
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19e7e01c44e25$6a834200$a601280a@.phx.gbl...[vbcol=seagreen]
> Will this restore the security, or will I have to restore
> the Master DB as well?
> databases back by
> (PASS) and it's
> message
> as
> I
> run
> I
> server?
a named instance, and I am trying to install SMS2003. I
have read in the documentation that SMS2003 cannot be run
on a named instance, and must be run on the default
instance.
Is there any way of switching the named instance to the
default instance, or does anyone have any ideas on how I
can overcome this problem without reinstalling SQL server?
Hi,
As far as I know, You need to reinstall SQL server to move from named to
default instance.
Thanks
Hari
MCDBA
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
> Our installation of SQL server 2000 has been installed as
> a named instance, and I am trying to install SMS2003. I
> have read in the documentation that SMS2003 cannot be run
> on a named instance, and must be run on the default
> instance.
> Is there any way of switching the named instance to the
> default instance, or does anyone have any ideas on how I
> can overcome this problem without reinstalling SQL server?
|||You will have to re-install SQL... But you can get your databases back by
backup/restore or sp_detach_db sp_attach_db
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
> Our installation of SQL server 2000 has been installed as
> a named instance, and I am trying to install SMS2003. I
> have read in the documentation that SMS2003 cannot be run
> on a named instance, and must be run on the default
> instance.
> Is there any way of switching the named instance to the
> default instance, or does anyone have any ideas on how I
> can overcome this problem without reinstalling SQL server?
|||Will this restore the security, or will I have to restore
the Master DB as well?
>--Original Message--
>You will have to re-install SQL... But you can get your
databases back by
>backup/restore or sp_detach_db sp_attach_db
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Mariner, Charlotte, NC
>www.mariner-usa.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"chris" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
as[vbcol=seagreen]
I[vbcol=seagreen]
run[vbcol=seagreen]
I[vbcol=seagreen]
server?
>
>.
>
|||Hi,
To restore the SQl Server Logins you have to restore the Master database as
well. This will ensure that your security chain is brought back as same as
old.
Master database can be restored only if you start sql server in single user
mode.
How to start SQl server in single user mode:-
Execute the below command from command prompt
sqlservr.exe -c -m
Thanks
Hari
MCDBA
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19e7e01c44e25$6a834200$a601280a@.phx.gbl...[vbcol=seagreen]
> Will this restore the security, or will I have to restore
> the Master DB as well?
> databases back by
> (PASS) and it's
> message
> as
> I
> run
> I
> server?
Default Instance
Our installation of SQL server 2000 has been installed as
a named instance, and I am trying to install SMS2003. I
have read in the documentation that SMS2003 cannot be run
on a named instance, and must be run on the default
instance.
Is there any way of switching the named instance to the
default instance, or does anyone have any ideas on how I
can overcome this problem without reinstalling SQL server?Hi,
As far as I know, You need to reinstall SQL server to move from named to
default instance.
--
Thanks
Hari
MCDBA
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
> Our installation of SQL server 2000 has been installed as
> a named instance, and I am trying to install SMS2003. I
> have read in the documentation that SMS2003 cannot be run
> on a named instance, and must be run on the default
> instance.
> Is there any way of switching the named instance to the
> default instance, or does anyone have any ideas on how I
> can overcome this problem without reinstalling SQL server?|||You will have to re-install SQL... But you can get your databases back by
backup/restore or sp_detach_db sp_attach_db
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
> Our installation of SQL server 2000 has been installed as
> a named instance, and I am trying to install SMS2003. I
> have read in the documentation that SMS2003 cannot be run
> on a named instance, and must be run on the default
> instance.
> Is there any way of switching the named instance to the
> default instance, or does anyone have any ideas on how I
> can overcome this problem without reinstalling SQL server?|||Will this restore the security, or will I have to restore
the Master DB as well?
>--Original Message--
>You will have to re-install SQL... But you can get your
databases back by
>backup/restore or sp_detach_db sp_attach_db
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Mariner, Charlotte, NC
>www.mariner-usa.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"chris" <anonymous@.discussions.microsoft.com> wrote in
message
>news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
>> Our installation of SQL server 2000 has been installed
as
>> a named instance, and I am trying to install SMS2003.
I
>> have read in the documentation that SMS2003 cannot be
run
>> on a named instance, and must be run on the default
>> instance.
>> Is there any way of switching the named instance to the
>> default instance, or does anyone have any ideas on how
I
>> can overcome this problem without reinstalling SQL
server?
>
>.
>|||Hi,
To restore the SQl Server Logins you have to restore the Master database as
well. This will ensure that your security chain is brought back as same as
old.
Master database can be restored only if you start sql server in single user
mode.
How to start SQl server in single user mode:-
Execute the below command from command prompt
sqlservr.exe -c -m
Thanks
Hari
MCDBA
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19e7e01c44e25$6a834200$a601280a@.phx.gbl...
> Will this restore the security, or will I have to restore
> the Master DB as well?
> >--Original Message--
> >You will have to re-install SQL... But you can get your
> databases back by
> >backup/restore or sp_detach_db sp_attach_db
> >
> >--
> >Wayne Snyder, MCDBA, SQL Server MVP
> >Mariner, Charlotte, NC
> >www.mariner-usa.com
> >(Please respond only to the newsgroups.)
> >
> >I support the Professional Association of SQL Server
> (PASS) and it's
> >community of SQL Server professionals.
> >www.sqlpass.org
> >
> >"chris" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
> >> Our installation of SQL server 2000 has been installed
> as
> >> a named instance, and I am trying to install SMS2003.
> I
> >> have read in the documentation that SMS2003 cannot be
> run
> >> on a named instance, and must be run on the default
> >> instance.
> >>
> >> Is there any way of switching the named instance to the
> >> default instance, or does anyone have any ideas on how
> I
> >> can overcome this problem without reinstalling SQL
> server?
> >
> >
> >.
> >
a named instance, and I am trying to install SMS2003. I
have read in the documentation that SMS2003 cannot be run
on a named instance, and must be run on the default
instance.
Is there any way of switching the named instance to the
default instance, or does anyone have any ideas on how I
can overcome this problem without reinstalling SQL server?Hi,
As far as I know, You need to reinstall SQL server to move from named to
default instance.
--
Thanks
Hari
MCDBA
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
> Our installation of SQL server 2000 has been installed as
> a named instance, and I am trying to install SMS2003. I
> have read in the documentation that SMS2003 cannot be run
> on a named instance, and must be run on the default
> instance.
> Is there any way of switching the named instance to the
> default instance, or does anyone have any ideas on how I
> can overcome this problem without reinstalling SQL server?|||You will have to re-install SQL... But you can get your databases back by
backup/restore or sp_detach_db sp_attach_db
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
> Our installation of SQL server 2000 has been installed as
> a named instance, and I am trying to install SMS2003. I
> have read in the documentation that SMS2003 cannot be run
> on a named instance, and must be run on the default
> instance.
> Is there any way of switching the named instance to the
> default instance, or does anyone have any ideas on how I
> can overcome this problem without reinstalling SQL server?|||Will this restore the security, or will I have to restore
the Master DB as well?
>--Original Message--
>You will have to re-install SQL... But you can get your
databases back by
>backup/restore or sp_detach_db sp_attach_db
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Mariner, Charlotte, NC
>www.mariner-usa.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"chris" <anonymous@.discussions.microsoft.com> wrote in
message
>news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
>> Our installation of SQL server 2000 has been installed
as
>> a named instance, and I am trying to install SMS2003.
I
>> have read in the documentation that SMS2003 cannot be
run
>> on a named instance, and must be run on the default
>> instance.
>> Is there any way of switching the named instance to the
>> default instance, or does anyone have any ideas on how
I
>> can overcome this problem without reinstalling SQL
server?
>
>.
>|||Hi,
To restore the SQl Server Logins you have to restore the Master database as
well. This will ensure that your security chain is brought back as same as
old.
Master database can be restored only if you start sql server in single user
mode.
How to start SQl server in single user mode:-
Execute the below command from command prompt
sqlservr.exe -c -m
Thanks
Hari
MCDBA
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19e7e01c44e25$6a834200$a601280a@.phx.gbl...
> Will this restore the security, or will I have to restore
> the Master DB as well?
> >--Original Message--
> >You will have to re-install SQL... But you can get your
> databases back by
> >backup/restore or sp_detach_db sp_attach_db
> >
> >--
> >Wayne Snyder, MCDBA, SQL Server MVP
> >Mariner, Charlotte, NC
> >www.mariner-usa.com
> >(Please respond only to the newsgroups.)
> >
> >I support the Professional Association of SQL Server
> (PASS) and it's
> >community of SQL Server professionals.
> >www.sqlpass.org
> >
> >"chris" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:19fd601c44e18$8ac5ffb0$a301280a@.phx.gbl...
> >> Our installation of SQL server 2000 has been installed
> as
> >> a named instance, and I am trying to install SMS2003.
> I
> >> have read in the documentation that SMS2003 cannot be
> run
> >> on a named instance, and must be run on the default
> >> instance.
> >>
> >> Is there any way of switching the named instance to the
> >> default instance, or does anyone have any ideas on how
> I
> >> can overcome this problem without reinstalling SQL
> server?
> >
> >
> >.
> >
Default Instance
Our installation of SQL server 2000 has been installed as
a named instance, and I am trying to install SMS2003. I
have read in the documentation that SMS2003 cannot be run
on a named instance, and must be run on the default
instance.
Is there any way of switching the named instance to the
default instance, or does anyone have any ideas on how I
can overcome this problem without reinstalling SQL server?Hi,
As far as I know, You need to reinstall SQL server to move from named to
default instance.
Thanks
Hari
MCDBA
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19fd601c44e18$8ac5ffb0$a301280a@.phx
.gbl...
> Our installation of SQL server 2000 has been installed as
> a named instance, and I am trying to install SMS2003. I
> have read in the documentation that SMS2003 cannot be run
> on a named instance, and must be run on the default
> instance.
> Is there any way of switching the named instance to the
> default instance, or does anyone have any ideas on how I
> can overcome this problem without reinstalling SQL server?|||You will have to re-install SQL... But you can get your databases back by
backup/restore or sp_detach_db sp_attach_db
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19fd601c44e18$8ac5ffb0$a301280a@.phx
.gbl...
> Our installation of SQL server 2000 has been installed as
> a named instance, and I am trying to install SMS2003. I
> have read in the documentation that SMS2003 cannot be run
> on a named instance, and must be run on the default
> instance.
> Is there any way of switching the named instance to the
> default instance, or does anyone have any ideas on how I
> can overcome this problem without reinstalling SQL server?|||Will this restore the security, or will I have to restore
the Master DB as well?
>--Original Message--
>You will have to re-install SQL... But you can get your
databases back by
>backup/restore or sp_detach_db sp_attach_db
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Mariner, Charlotte, NC
>www.mariner-usa.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"chris" <anonymous@.discussions.microsoft.com> wrote in
message
> news:19fd601c44e18$8ac5ffb0$a301280a@.phx
.gbl...
as[vbcol=seagreen]
I[vbcol=seagreen]
run[vbcol=seagreen]
I[vbcol=seagreen]
server?[vbcol=seagreen]
>
>.
>|||Hi,
To restore the SQl Server Logins you have to restore the Master database as
well. This will ensure that your security chain is brought back as same as
old.
Master database can be restored only if you start sql server in single user
mode.
How to start SQl server in single user mode:-
Execute the below command from command prompt
sqlservr.exe -c -m
Thanks
Hari
MCDBA
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19e7e01c44e25$6a834200$a601280a@.phx
.gbl...[vbcol=seagreen]
> Will this restore the security, or will I have to restore
> the Master DB as well?
>
> databases back by
> (PASS) and it's
> message
> as
> I
> run
> I
> server?sql
a named instance, and I am trying to install SMS2003. I
have read in the documentation that SMS2003 cannot be run
on a named instance, and must be run on the default
instance.
Is there any way of switching the named instance to the
default instance, or does anyone have any ideas on how I
can overcome this problem without reinstalling SQL server?Hi,
As far as I know, You need to reinstall SQL server to move from named to
default instance.
Thanks
Hari
MCDBA
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19fd601c44e18$8ac5ffb0$a301280a@.phx
.gbl...
> Our installation of SQL server 2000 has been installed as
> a named instance, and I am trying to install SMS2003. I
> have read in the documentation that SMS2003 cannot be run
> on a named instance, and must be run on the default
> instance.
> Is there any way of switching the named instance to the
> default instance, or does anyone have any ideas on how I
> can overcome this problem without reinstalling SQL server?|||You will have to re-install SQL... But you can get your databases back by
backup/restore or sp_detach_db sp_attach_db
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19fd601c44e18$8ac5ffb0$a301280a@.phx
.gbl...
> Our installation of SQL server 2000 has been installed as
> a named instance, and I am trying to install SMS2003. I
> have read in the documentation that SMS2003 cannot be run
> on a named instance, and must be run on the default
> instance.
> Is there any way of switching the named instance to the
> default instance, or does anyone have any ideas on how I
> can overcome this problem without reinstalling SQL server?|||Will this restore the security, or will I have to restore
the Master DB as well?
>--Original Message--
>You will have to re-install SQL... But you can get your
databases back by
>backup/restore or sp_detach_db sp_attach_db
>--
>Wayne Snyder, MCDBA, SQL Server MVP
>Mariner, Charlotte, NC
>www.mariner-usa.com
>(Please respond only to the newsgroups.)
>I support the Professional Association of SQL Server
(PASS) and it's
>community of SQL Server professionals.
>www.sqlpass.org
>"chris" <anonymous@.discussions.microsoft.com> wrote in
message
> news:19fd601c44e18$8ac5ffb0$a301280a@.phx
.gbl...
as[vbcol=seagreen]
I[vbcol=seagreen]
run[vbcol=seagreen]
I[vbcol=seagreen]
server?[vbcol=seagreen]
>
>.
>|||Hi,
To restore the SQl Server Logins you have to restore the Master database as
well. This will ensure that your security chain is brought back as same as
old.
Master database can be restored only if you start sql server in single user
mode.
How to start SQl server in single user mode:-
Execute the below command from command prompt
sqlservr.exe -c -m
Thanks
Hari
MCDBA
"Chris" <anonymous@.discussions.microsoft.com> wrote in message
news:19e7e01c44e25$6a834200$a601280a@.phx
.gbl...[vbcol=seagreen]
> Will this restore the security, or will I have to restore
> the Master DB as well?
>
> databases back by
> (PASS) and it's
> message
> as
> I
> run
> I
> server?sql
Thursday, March 22, 2012
Default data and log file location
How can I determine the default data and log file locations of a Smo.Server instance?
For example, my server's default location is "C:\Program Files\Microsoft SQL Server\MSSQL\Data"
Hi,
you can use the following code to get the registry values, but the documentation is not right at this point as I won′t bring back any string if not set in the registry:
Server s = new Server(".");
Console.WriteLine(s.Settings.DefaultFile);
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||
Thanks - thats what I was looking for. When the registry value is not set I will just grab the file location of the master db:
'open the master database
Dim master As Database = New Database(_server, "master")
master.Refresh()
'get the location of its mdf file
Dim masterMdfFilename = master.FileGroups.Item(0).Files.Item(0).FileName
Console.WriteLine(System.IO.Path.GetDirectoryName(masterMdfFilename))
Default data and log file location
How can I determine the default data and log file locations of a Smo.Server instance?
For example, my server's default location is "C:\Program Files\Microsoft SQL Server\MSSQL\Data"
Hi,
you can use the following code to get the registry values, but the documentation is not right at this point as I won′t bring back any string if not set in the registry:
Server s = new Server(".");
Console.WriteLine(s.Settings.DefaultFile);
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||
Thanks - thats what I was looking for. When the registry value is not set I will just grab the file location of the master db:
'open the master database
Dim master As Database = New Database(_server, "master")
master.Refresh()
'get the location of its mdf file
Dim masterMdfFilename = master.FileGroups.Item(0).Files.Item(0).FileName
Console.WriteLine(System.IO.Path.GetDirectoryName(masterMdfFilename))
Wednesday, March 21, 2012
Dedupe Priority Logic (within Sort) - feature request?
Is there a way to specify which record is chosen when deduping records using the Sort component? for instance, you might want to choose the last record in for all records with matching sort keys by picking the record with the max(create_date).
By default what record does the sort component pick as the record to be output - first one in finds?
This would be a great feature - a new data flow transform called "Dedupe" that has some powerful deduping features.I think you can achieve what you're talking about by using an Aggregate transform, possibly in conjuction with a Sort.
Dedupe Priority Logic (within Sort) - feature request?
Is there a way to specify which record is chosen when deduping records using the Sort component? for instance, you might want to choose the last record in for all records with matching sort keys by picking the record with the max(create_date).
By default what record does the sort component pick as the record to be output - first one in finds?
This would be a great feature - a new data flow transform called "Dedupe" that has some powerful deduping features.I think you can achieve what you're talking about by using an Aggregate transform, possibly in conjuction with a Sort.
Dedicated Administrator Connection
Hi:
I am trying to connect to my local instance of SQL Server 2005 using Dedicated Administrator Connection by using
Admin:Servername\Instancename
and I end up with the following error.
Dedicated administrator connections are not supported.
I enabled the connection in the SQL Configuration Manager and still get the error.
Any ideas on how to resolve this error?.
Note: SQL Browser service is running.
Thanks
Ak
Which SKU of sql server 2005 are you running ?
Also, are the client and the server running on the same machine or different machines ?
|||Hi Asvin:
I am running SQL Server 2005 Standard Edition and both the client and server are running on the same machine.
Thanks
|||You can check the sqlserver log to see if DAC is enabled/listening (and on which tcp port).Use sqlcmd -A to test. Also, you cannot use DAC for Object Explorer connection. It only works on query window. So, connect normally first, then open a new query window with "admin:<server>\<instance>"|||
Hi OJ:
Thanks for your reply.
This is what my SQL Server log says.
Date 7/7/2006 4:56:11 PM
Log SQL Server (Current - 7/12/2006 12:00:00 AM)
Source Server
Message
Dedicated admin connection support was established for listening remotely on port 1771.
So DAC is listening on port 1771 right?. I tried your second method of connecting to through object explorer but I got the same error message.
Then I tried the following from command prompt:
sqlcmd -SMyMachine\SQL2K5 -A -E
I got the following error message:
HResult 0xFFFFFFFF, Level 16, State 1
SQL Network Interfaces: An error occurred while obtaining the dedicated administrator connection (DAC) port.
Make sure that SQL Browser is running, or check the error log for the port number [xFFFFFFFF].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings
SQL Server does not allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
Please let me know what I am doing wrong.
Thanks
|||MS Experts:
Can anyone please help me with this issue. I would really appreciate all your help.
Thanks
AK
|||Sorry for the late reply.I've seen the same error when the server\instance is incorrect. Since this is a local instance, please try one of the following:
sqlcmd -S".\SQL2K5" -A -E
sqlcmd -S"MyMachine,1771" -A -E
Be sure to start the instance first.
net start mssql$sql2k5
|||
Did you enable remote connections ?
http://www.sqlserver2005.de/SharedFiles/Remoteconnection.jpg
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Thanks OJ and Jens. I tried all options that you have suggested (my remote connections are enabled) but still get the same error.
The funny thing is when I try through the command prompt using sqlcmd (with the new commands you gave) it appears to be connected but when I connect using SQL Management Studio while the command window is still open, it allows me to establish a new connection through Management studio. I think once DAC is established i should not be able to make a new connection using management studio. DAC should allow only a single connection. This tells me that a DAC was not establised through SQLCMD from command prompt.
So to make sure that I can indeed connect using DAC I used the SQL Management Studioand tried the following:
ADMIN:.\SQL2K5 and end up with the same error.
Dedicated adminstrator connections are not supported.
This means I am not able to connect using DAC still.
I cant post the attachment or else I would have posted the attachment.
|||There can only be ONE admin connection. If you successfully connect via "sqlcmd -A" then you will not be able to make another admin connection via sqlwb (vice versa).Admin connection has nothing to do with regular user connection. So, it's normal that you still can connect via sqlwb. However, it will not be possible for you to open another admin connection (i.e. admin:\.sql2k5) via sqlwb if you already connect with sqlcmd.
As I have said before, you need to connect normally (without admin) when you first open up sqlwb. Once that's done, you can open a new query window (File -> New -> Database Engine Query) and connect as an admin connection.
If you still have problem, please post the entire sql log here.|||
Do you obtain this error message:
"Dedicated administrator connections are not supported. (ObjectExplorer)"
If so you try to connect the Object Explorer. Try to open a new query windows as oj told you.
|||
Thanks everyone. I seem to have connected through the cmd prompt through DAC and when I query using @.@.Servername I can see my machine name in the cmd prompt window. I am just wondering if there is a command in SQL Server 2005 that tells me whether I am connected using dedicated admin connection or that my present connection is a DAC. If so, I would appreciate if if anyone lets me know it.
Thanks
AK.
|||The query below should return 1 row if you are connected using dedicated admin connection. It should not return any rows if you are not connected using DAC.
select * from sys.dm_exec_connections ec join sys.endpoints e on (ec.endpoint_id=e.endpoint_id) where e.name='Dedicated Admin Connection' and session_id=@.@.spid
|||Thanks Ashvin. That did exactly confirm that I was connected using DAC. It returned one row. So my million dollar question is why cant I connect to DAC using ADMIN keyword. I tried all that have been suggested in this thread and still it says DAC connections are not supported (Object Explorer). Its a mystery!!!.
However thanks for all the suggestions.
|||Hi,
DAC is a feature which is disabled by default. Did you enable it so far ? I made a screencast for you showing how to enable this feature. This is the second of a series which I decided to make. So have Fun !
A link with the screencasts taken so far will be on my site as I will have time for that.
use this link here in the meantime: http://www.SQLServer2005.de/ScreenCasts/Enable_DAC.htm
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
Subscribe to:
Posts (Atom)