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
Showing posts with label setup. Show all posts
Showing posts with label setup. Show all posts
Thursday, March 29, 2012
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
Tuesday, March 27, 2012
Default installation
I have built an application that uses SQLExpress. When I build the setup with a new setup Project I include in the prerequisites SQLExpress so that if the target PC has no SQL server installed the setup sequence will automatically install an instance.
The Serup Sequence installes SQL Server with default Instance name and settings. I need to make the setup package to install the SQL instance with a specific name and some other setting. These settings would be
/qb ADDLOCAL=ALL SECURITYMODE=SQL SAPWD=pass INSTANCENAME=instname DISABLENETWORKPROTOCOLS=0
if i run it from Command Line.
I searched a lot on my own and didnt find any way of predefining these setting. Tnx in advance
The instance name is hard coded into the manifests used to generate the SQL Express prerequisite and there is no way to dynamically change it. You would need to go in and alter the command line used to install SQL Express that is encoded in the manifest.
You can find more about how the prerequisties in VS work by searching MSDN for "generic bootstrapper". I've also posted instruction on how to build your own prerequisite for SQL Express SP2 (VS only has RTM) that may be instructive. My sample also installs to the default named instance, but again, you can make any changes you want. Check out this blog post for more information.
Finally, you can choose to write your own install wrapper and take full control over the installation process. There is a white paper that discusses how to embed SQL Express installation in a custom wrapper here.
Mike
Default installation
I have built an application that uses SQLExpress. When I build the setup with a new setup Project I include in the prerequisites SQLExpress so that if the target PC has no SQL server installed the setup sequence will automatically install an instance.
The Serup Sequence installes SQL Server with default Instance name and settings. I need to make the setup package to install the SQL instance with a specific name and some other setting. These settings would be
/qb ADDLOCAL=ALL SECURITYMODE=SQL SAPWD=pass INSTANCENAME=instname DISABLENETWORKPROTOCOLS=0
if i run it from Command Line.
I searched a lot on my own and didnt find any way of predefining these setting. Tnx in advance
The instance name is hard coded into the manifests used to generate the SQL Express prerequisite and there is no way to dynamically change it. You would need to go in and alter the command line used to install SQL Express that is encoded in the manifest.
You can find more about how the prerequisties in VS work by searching MSDN for "generic bootstrapper". I've also posted instruction on how to build your own prerequisite for SQL Express SP2 (VS only has RTM) that may be instructive. My sample also installs to the default named instance, but again, you can make any changes you want. Check out this blog post for more information.
Finally, you can choose to write your own install wrapper and take full control over the installation process. There is a white paper that discusses how to embed SQL Express installation in a custom wrapper here.
Mike
sqlSunday, March 25, 2012
Default database location?
I have the default location for Data setup to be G:\Microsoft SQL
Server\Data (Database Settings under server properties).
But, when I invoke "Copy Database" from Management, it places the data on
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
Why doesn't the Copy Database Wizard respect my setting?
OlavOlav
It probably takes it from a model database
SELECT REPLACE(filename, 'model.mdf', '') FROM master..SysDatabases
WHERE [name] = 'model'
"Olav" <x@.y.com> wrote in message
news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>I have the default location for Data setup to be G:\Microsoft SQL
>Server\Data (Database Settings under server properties).
> But, when I invoke "Copy Database" from Management, it places the data on
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
> Why doesn't the Copy Database Wizard respect my setting?
> Olav
>|||I'm confused!
Why are there multiple places to configure the same kind of option?
Olav
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uUaZJ8WXGHA.4248@.TK2MSFTNGP05.phx.gbl...
> Olav
> It probably takes it from a model database
> SELECT REPLACE(filename, 'model.mdf', '') FROM master..SysDatabases
> WHERE [name] = 'model'
>
>
>
> "Olav" <x@.y.com> wrote in message
> news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>|||You can view the default directory with the following :-
exec master..xp_regread
'HKEY_LOCAL_MACHINE','SOFTWARE\Microsoft
\MSSQLServer\Setup','SQLDataRoot'
It can be changed with EnterPrise Manager, but... this change may not stick
as you need sufficient permsion to write to registry. If you find it isn't
saving you will need to logon to the box as administrator.
HTH. Ryan
"Olav" <x@.y.com> wrote in message
news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>I have the default location for Data setup to be G:\Microsoft SQL
>Server\Data (Database Settings under server properties).
> But, when I invoke "Copy Database" from Management, it places the data on
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
> Why doesn't the Copy Database Wizard respect my setting?
> Olav
>|||This is the result I got from the query on that machine:
RegQueryValueEx() returned error 2, 'The system cannot find the file
specified.'
Msg 22001, Level 1, State 1
(0 row(s) affected)
What does this indicate?
Olav
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:uDgpjEXXGHA.1196@.TK2MSFTNGP03.phx.gbl...
> You can view the default directory with the following :-
> exec master..xp_regread
> 'HKEY_LOCAL_MACHINE','SOFTWARE\Microsoft
\MSSQLServer\Setup','SQLDataRoot'
> It can be changed with EnterPrise Manager, but... this change may not
> stick as you need sufficient permsion to write to registry. If you find it
> isn't saving you will need to logon to the box as administrator.
> --
> HTH. Ryan
>
> "Olav" <x@.y.com> wrote in message
> news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>|||I checked in the Registry and it shows the following value for that key:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
In SQL Server Management Studio it shows:
G:\Microsoft SQL Server\Data
I'm still confused!
Why are there two different values for the same thing stored?
I'm running Management Studio logged in as an Administrator, so there should
be no problem writing to the registry.
Olav
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:uDgpjEXXGHA.1196@.TK2MSFTNGP03.phx.gbl...
> You can view the default directory with the following :-
> exec master..xp_regread
> 'HKEY_LOCAL_MACHINE','SOFTWARE\Microsoft
\MSSQLServer\Setup','SQLDataRoot'
> It can be changed with EnterPrise Manager, but... this change may not
> stick as you need sufficient permsion to write to registry. If you find it
> isn't saving you will need to logon to the box as administrator.
> --
> HTH. Ryan
>
> "Olav" <x@.y.com> wrote in message
> news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>
Server\Data (Database Settings under server properties).
But, when I invoke "Copy Database" from Management, it places the data on
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
Why doesn't the Copy Database Wizard respect my setting?
OlavOlav
It probably takes it from a model database
SELECT REPLACE(filename, 'model.mdf', '') FROM master..SysDatabases
WHERE [name] = 'model'
"Olav" <x@.y.com> wrote in message
news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>I have the default location for Data setup to be G:\Microsoft SQL
>Server\Data (Database Settings under server properties).
> But, when I invoke "Copy Database" from Management, it places the data on
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
> Why doesn't the Copy Database Wizard respect my setting?
> Olav
>|||I'm confused!
Why are there multiple places to configure the same kind of option?
Olav
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uUaZJ8WXGHA.4248@.TK2MSFTNGP05.phx.gbl...
> Olav
> It probably takes it from a model database
> SELECT REPLACE(filename, 'model.mdf', '') FROM master..SysDatabases
> WHERE [name] = 'model'
>
>
>
> "Olav" <x@.y.com> wrote in message
> news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>|||You can view the default directory with the following :-
exec master..xp_regread
'HKEY_LOCAL_MACHINE','SOFTWARE\Microsoft
\MSSQLServer\Setup','SQLDataRoot'
It can be changed with EnterPrise Manager, but... this change may not stick
as you need sufficient permsion to write to registry. If you find it isn't
saving you will need to logon to the box as administrator.
HTH. Ryan
"Olav" <x@.y.com> wrote in message
news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>I have the default location for Data setup to be G:\Microsoft SQL
>Server\Data (Database Settings under server properties).
> But, when I invoke "Copy Database" from Management, it places the data on
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
> Why doesn't the Copy Database Wizard respect my setting?
> Olav
>|||This is the result I got from the query on that machine:
RegQueryValueEx() returned error 2, 'The system cannot find the file
specified.'
Msg 22001, Level 1, State 1
(0 row(s) affected)
What does this indicate?
Olav
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:uDgpjEXXGHA.1196@.TK2MSFTNGP03.phx.gbl...
> You can view the default directory with the following :-
> exec master..xp_regread
> 'HKEY_LOCAL_MACHINE','SOFTWARE\Microsoft
\MSSQLServer\Setup','SQLDataRoot'
> It can be changed with EnterPrise Manager, but... this change may not
> stick as you need sufficient permsion to write to registry. If you find it
> isn't saving you will need to logon to the box as administrator.
> --
> HTH. Ryan
>
> "Olav" <x@.y.com> wrote in message
> news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>|||I checked in the Registry and it shows the following value for that key:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
In SQL Server Management Studio it shows:
G:\Microsoft SQL Server\Data
I'm still confused!
Why are there two different values for the same thing stored?
I'm running Management Studio logged in as an Administrator, so there should
be no problem writing to the registry.
Olav
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:uDgpjEXXGHA.1196@.TK2MSFTNGP03.phx.gbl...
> You can view the default directory with the following :-
> exec master..xp_regread
> 'HKEY_LOCAL_MACHINE','SOFTWARE\Microsoft
\MSSQLServer\Setup','SQLDataRoot'
> It can be changed with EnterPrise Manager, but... this change may not
> stick as you need sufficient permsion to write to registry. If you find it
> isn't saving you will need to logon to the box as administrator.
> --
> HTH. Ryan
>
> "Olav" <x@.y.com> wrote in message
> news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>
Default database location?
I have the default location for Data setup to be G:\Microsoft SQL
Server\Data (Database Settings under server properties).
But, when I invoke "Copy Database" from Management, it places the data on
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
Why doesn't the Copy Database Wizard respect my setting?
OlavOlav
It probably takes it from a model database
SELECT REPLACE(filename, 'model.mdf', '') FROM master..SysDatabases
WHERE [name] = 'model'
"Olav" <x@.y.com> wrote in message
news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>I have the default location for Data setup to be G:\Microsoft SQL
>Server\Data (Database Settings under server properties).
> But, when I invoke "Copy Database" from Management, it places the data on
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
> Why doesn't the Copy Database Wizard respect my setting?
> Olav
>|||I'm confused!
Why are there multiple places to configure the same kind of option?
Olav
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uUaZJ8WXGHA.4248@.TK2MSFTNGP05.phx.gbl...
> Olav
> It probably takes it from a model database
> SELECT REPLACE(filename, 'model.mdf', '') FROM master..SysDatabases
> WHERE [name] = 'model'
>
>
>
> "Olav" <x@.y.com> wrote in message
> news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>>I have the default location for Data setup to be G:\Microsoft SQL
>>Server\Data (Database Settings under server properties).
>> But, when I invoke "Copy Database" from Management, it places the data on
>> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
>> Why doesn't the Copy Database Wizard respect my setting?
>> Olav
>|||You can view the default directory with the following :-
exec master..xp_regread
'HKEY_LOCAL_MACHINE','SOFTWARE\Microsoft\MSSQLServer\Setup','SQLDataRoot'
It can be changed with EnterPrise Manager, but... this change may not stick
as you need sufficient permsion to write to registry. If you find it isn't
saving you will need to logon to the box as administrator.
--
HTH. Ryan
"Olav" <x@.y.com> wrote in message
news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>I have the default location for Data setup to be G:\Microsoft SQL
>Server\Data (Database Settings under server properties).
> But, when I invoke "Copy Database" from Management, it places the data on
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
> Why doesn't the Copy Database Wizard respect my setting?
> Olav
>|||This is the result I got from the query on that machine:
RegQueryValueEx() returned error 2, 'The system cannot find the file
specified.'
Msg 22001, Level 1, State 1
(0 row(s) affected)
What does this indicate?
Olav
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:uDgpjEXXGHA.1196@.TK2MSFTNGP03.phx.gbl...
> You can view the default directory with the following :-
> exec master..xp_regread
> 'HKEY_LOCAL_MACHINE','SOFTWARE\Microsoft\MSSQLServer\Setup','SQLDataRoot'
> It can be changed with EnterPrise Manager, but... this change may not
> stick as you need sufficient permsion to write to registry. If you find it
> isn't saving you will need to logon to the box as administrator.
> --
> HTH. Ryan
>
> "Olav" <x@.y.com> wrote in message
> news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>>I have the default location for Data setup to be G:\Microsoft SQL
>>Server\Data (Database Settings under server properties).
>> But, when I invoke "Copy Database" from Management, it places the data on
>> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
>> Why doesn't the Copy Database Wizard respect my setting?
>> Olav
>|||I checked in the Registry and it shows the following value for that key:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
In SQL Server Management Studio it shows:
G:\Microsoft SQL Server\Data
I'm still confused!
Why are there two different values for the same thing stored?
I'm running Management Studio logged in as an Administrator, so there should
be no problem writing to the registry.
Olav
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:uDgpjEXXGHA.1196@.TK2MSFTNGP03.phx.gbl...
> You can view the default directory with the following :-
> exec master..xp_regread
> 'HKEY_LOCAL_MACHINE','SOFTWARE\Microsoft\MSSQLServer\Setup','SQLDataRoot'
> It can be changed with EnterPrise Manager, but... this change may not
> stick as you need sufficient permsion to write to registry. If you find it
> isn't saving you will need to logon to the box as administrator.
> --
> HTH. Ryan
>
> "Olav" <x@.y.com> wrote in message
> news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>>I have the default location for Data setup to be G:\Microsoft SQL
>>Server\Data (Database Settings under server properties).
>> But, when I invoke "Copy Database" from Management, it places the data on
>> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
>> Why doesn't the Copy Database Wizard respect my setting?
>> Olav
>
Server\Data (Database Settings under server properties).
But, when I invoke "Copy Database" from Management, it places the data on
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
Why doesn't the Copy Database Wizard respect my setting?
OlavOlav
It probably takes it from a model database
SELECT REPLACE(filename, 'model.mdf', '') FROM master..SysDatabases
WHERE [name] = 'model'
"Olav" <x@.y.com> wrote in message
news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>I have the default location for Data setup to be G:\Microsoft SQL
>Server\Data (Database Settings under server properties).
> But, when I invoke "Copy Database" from Management, it places the data on
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
> Why doesn't the Copy Database Wizard respect my setting?
> Olav
>|||I'm confused!
Why are there multiple places to configure the same kind of option?
Olav
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uUaZJ8WXGHA.4248@.TK2MSFTNGP05.phx.gbl...
> Olav
> It probably takes it from a model database
> SELECT REPLACE(filename, 'model.mdf', '') FROM master..SysDatabases
> WHERE [name] = 'model'
>
>
>
> "Olav" <x@.y.com> wrote in message
> news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>>I have the default location for Data setup to be G:\Microsoft SQL
>>Server\Data (Database Settings under server properties).
>> But, when I invoke "Copy Database" from Management, it places the data on
>> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
>> Why doesn't the Copy Database Wizard respect my setting?
>> Olav
>|||You can view the default directory with the following :-
exec master..xp_regread
'HKEY_LOCAL_MACHINE','SOFTWARE\Microsoft\MSSQLServer\Setup','SQLDataRoot'
It can be changed with EnterPrise Manager, but... this change may not stick
as you need sufficient permsion to write to registry. If you find it isn't
saving you will need to logon to the box as administrator.
--
HTH. Ryan
"Olav" <x@.y.com> wrote in message
news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>I have the default location for Data setup to be G:\Microsoft SQL
>Server\Data (Database Settings under server properties).
> But, when I invoke "Copy Database" from Management, it places the data on
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
> Why doesn't the Copy Database Wizard respect my setting?
> Olav
>|||This is the result I got from the query on that machine:
RegQueryValueEx() returned error 2, 'The system cannot find the file
specified.'
Msg 22001, Level 1, State 1
(0 row(s) affected)
What does this indicate?
Olav
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:uDgpjEXXGHA.1196@.TK2MSFTNGP03.phx.gbl...
> You can view the default directory with the following :-
> exec master..xp_regread
> 'HKEY_LOCAL_MACHINE','SOFTWARE\Microsoft\MSSQLServer\Setup','SQLDataRoot'
> It can be changed with EnterPrise Manager, but... this change may not
> stick as you need sufficient permsion to write to registry. If you find it
> isn't saving you will need to logon to the box as administrator.
> --
> HTH. Ryan
>
> "Olav" <x@.y.com> wrote in message
> news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>>I have the default location for Data setup to be G:\Microsoft SQL
>>Server\Data (Database Settings under server properties).
>> But, when I invoke "Copy Database" from Management, it places the data on
>> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
>> Why doesn't the Copy Database Wizard respect my setting?
>> Olav
>|||I checked in the Registry and it shows the following value for that key:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
In SQL Server Management Studio it shows:
G:\Microsoft SQL Server\Data
I'm still confused!
Why are there two different values for the same thing stored?
I'm running Management Studio logged in as an Administrator, so there should
be no problem writing to the registry.
Olav
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:uDgpjEXXGHA.1196@.TK2MSFTNGP03.phx.gbl...
> You can view the default directory with the following :-
> exec master..xp_regread
> 'HKEY_LOCAL_MACHINE','SOFTWARE\Microsoft\MSSQLServer\Setup','SQLDataRoot'
> It can be changed with EnterPrise Manager, but... this change may not
> stick as you need sufficient permsion to write to registry. If you find it
> isn't saving you will need to logon to the box as administrator.
> --
> HTH. Ryan
>
> "Olav" <x@.y.com> wrote in message
> news:%23xMVx0WXGHA.1348@.TK2MSFTNGP05.phx.gbl...
>>I have the default location for Data setup to be G:\Microsoft SQL
>>Server\Data (Database Settings under server properties).
>> But, when I invoke "Copy Database" from Management, it places the data on
>> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA.
>> Why doesn't the Copy Database Wizard respect my setting?
>> Olav
>
Thursday, March 22, 2012
Default Backup Location
Where do I setup the default backup folder location on SQL Server 2005?
Thanks,
Ademar.I didn't find a way to set it with the GUI, but you can always modify the registry. On my machine, I
have a path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer
And there is a key named BackupDirectory
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ademar" <ademar@.nospam.com> wrote in message news:OZ9D5YvbGHA.3344@.TK2MSFTNGP03.phx.gbl...
> Where do I setup the default backup folder location on SQL Server 2005?
> Thanks,
> Ademar.
>
Thanks,
Ademar.I didn't find a way to set it with the GUI, but you can always modify the registry. On my machine, I
have a path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer
And there is a key named BackupDirectory
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ademar" <ademar@.nospam.com> wrote in message news:OZ9D5YvbGHA.3344@.TK2MSFTNGP03.phx.gbl...
> Where do I setup the default backup folder location on SQL Server 2005?
> Thanks,
> Ademar.
>
Default Backup Location
Where do I setup the default backup folder location on SQL Server 2005?
Thanks,
Ademar.I didn't find a way to set it with the GUI, but you can always modify the re
gistry. On my machine, I
have a path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL Server\MSSQL.1\MSSQLServ
er
And there is a key named BackupDirectory
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ademar" <ademar@.nospam.com> wrote in message news:OZ9D5YvbGHA.3344@.TK2MSFTNGP03.phx.gbl...[
vbcol=seagreen]
> Where do I setup the default backup folder location on SQL Server 2005?
> Thanks,
> Ademar.
>[/vbcol]sql
Thanks,
Ademar.I didn't find a way to set it with the GUI, but you can always modify the re
gistry. On my machine, I
have a path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL Server\MSSQL.1\MSSQLServ
er
And there is a key named BackupDirectory
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ademar" <ademar@.nospam.com> wrote in message news:OZ9D5YvbGHA.3344@.TK2MSFTNGP03.phx.gbl...[
vbcol=seagreen]
> Where do I setup the default backup folder location on SQL Server 2005?
> Thanks,
> Ademar.
>[/vbcol]sql
Saturday, February 25, 2012
Debugging triggers on views in SQL Server 2005?
I am trying to debug an "INSTEAD OF INSERT" trigger on a view in SQL Server
2005. I setup a stored procedure to insert to the view, then (in Visual
Studio) put a stop in the stored procedure. This works fine, until I try to
step into the trigger. Then it tells me that no code is available.
If I try in Visual Studio 2005 to set a breakpoint on this trigger, it won't
allow me, saying "A breakpoint could not be inserted at this location".
This only happens for any trigger on the view. If I try to set a breakpoint
on a trigger on a table, it works fine.
Does anyone know a way around this? I really would like to step though the
trigger on the view.Is anyone going to respond to this? I thought these news groups were managed
and a response could be expected in 48 hours.
"BrianInHouston" wrote:
> I am trying to debug an "INSTEAD OF INSERT" trigger on a view in SQL Server
> 2005. I setup a stored procedure to insert to the view, then (in Visual
> Studio) put a stop in the stored procedure. This works fine, until I try to
> step into the trigger. Then it tells me that no code is available.
> If I try in Visual Studio 2005 to set a breakpoint on this trigger, it won't
> allow me, saying "A breakpoint could not be inserted at this location".
> This only happens for any trigger on the view. If I try to set a breakpoint
> on a trigger on a table, it works fine.
> Does anyone know a way around this? I really would like to step though the
> trigger on the view.|||I don't know the answer to the debugging question, but yes, if you're an
MSDN subscriber and posted this using the account you registered when you
signed up for managed newsgroups, you should get a response within 2
business days. If you don't, the FAQ page points you at
https://support.microsoft.com/common/survey.aspx?scid=sw;en;1296&showpage=1&ws=msdn&sd=msdn&pa=msdnw
to contact the folks at MSDN about it.
The first thing to do, however, is to ensure that the alias that you're
posting with is registered properly. To do that, go to
http://msdn.microsoft.com/subscriptions/, sign in, and click the Managed
Newsgroups link.
--
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"BrianInHouston" <BrianInHouston@.discussions.microsoft.com> wrote in message
news:66D6AC1C-BB18-4FC4-B30C-F94D33A441E2@.microsoft.com...
> Is anyone going to respond to this? I thought these news groups were
> managed
> and a response could be expected in 48 hours.
> "BrianInHouston" wrote:
>> I am trying to debug an "INSTEAD OF INSERT" trigger on a view in SQL
>> Server
>> 2005. I setup a stored procedure to insert to the view, then (in Visual
>> Studio) put a stop in the stored procedure. This works fine, until I try
>> to
>> step into the trigger. Then it tells me that no code is available.
>> If I try in Visual Studio 2005 to set a breakpoint on this trigger, it
>> won't
>> allow me, saying "A breakpoint could not be inserted at this location".
>> This only happens for any trigger on the view. If I try to set a
>> breakpoint
>> on a trigger on a table, it works fine.
>> Does anyone know a way around this? I really would like to step though
>> the
>> trigger on the view.
2005. I setup a stored procedure to insert to the view, then (in Visual
Studio) put a stop in the stored procedure. This works fine, until I try to
step into the trigger. Then it tells me that no code is available.
If I try in Visual Studio 2005 to set a breakpoint on this trigger, it won't
allow me, saying "A breakpoint could not be inserted at this location".
This only happens for any trigger on the view. If I try to set a breakpoint
on a trigger on a table, it works fine.
Does anyone know a way around this? I really would like to step though the
trigger on the view.Is anyone going to respond to this? I thought these news groups were managed
and a response could be expected in 48 hours.
"BrianInHouston" wrote:
> I am trying to debug an "INSTEAD OF INSERT" trigger on a view in SQL Server
> 2005. I setup a stored procedure to insert to the view, then (in Visual
> Studio) put a stop in the stored procedure. This works fine, until I try to
> step into the trigger. Then it tells me that no code is available.
> If I try in Visual Studio 2005 to set a breakpoint on this trigger, it won't
> allow me, saying "A breakpoint could not be inserted at this location".
> This only happens for any trigger on the view. If I try to set a breakpoint
> on a trigger on a table, it works fine.
> Does anyone know a way around this? I really would like to step though the
> trigger on the view.|||I don't know the answer to the debugging question, but yes, if you're an
MSDN subscriber and posted this using the account you registered when you
signed up for managed newsgroups, you should get a response within 2
business days. If you don't, the FAQ page points you at
https://support.microsoft.com/common/survey.aspx?scid=sw;en;1296&showpage=1&ws=msdn&sd=msdn&pa=msdnw
to contact the folks at MSDN about it.
The first thing to do, however, is to ensure that the alias that you're
posting with is registered properly. To do that, go to
http://msdn.microsoft.com/subscriptions/, sign in, and click the Managed
Newsgroups link.
--
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"BrianInHouston" <BrianInHouston@.discussions.microsoft.com> wrote in message
news:66D6AC1C-BB18-4FC4-B30C-F94D33A441E2@.microsoft.com...
> Is anyone going to respond to this? I thought these news groups were
> managed
> and a response could be expected in 48 hours.
> "BrianInHouston" wrote:
>> I am trying to debug an "INSTEAD OF INSERT" trigger on a view in SQL
>> Server
>> 2005. I setup a stored procedure to insert to the view, then (in Visual
>> Studio) put a stop in the stored procedure. This works fine, until I try
>> to
>> step into the trigger. Then it tells me that no code is available.
>> If I try in Visual Studio 2005 to set a breakpoint on this trigger, it
>> won't
>> allow me, saying "A breakpoint could not be inserted at this location".
>> This only happens for any trigger on the view. If I try to set a
>> breakpoint
>> on a trigger on a table, it works fine.
>> Does anyone know a way around this? I really would like to step though
>> the
>> trigger on the view.
Debugging triggers on views in SQL Server 2005?
I am trying to debug an "INSTEAD OF INSERT" trigger on a view in SQL Server
2005. I setup a stored procedure to insert to the view, then (in Visual
Studio) put a stop in the stored procedure. This works fine, until I try to
step into the trigger. Then it tells me that no code is available.
If I try in Visual Studio 2005 to set a breakpoint on this trigger, it won't
allow me, saying "A breakpoint could not be inserted at this location".
This only happens for any trigger on the view. If I try to set a breakpoint
on a trigger on a table, it works fine.
Does anyone know a way around this? I really would like to step though the
trigger on the view.Is anyone going to respond to this? I thought these news groups were manage
d
and a response could be expected in 48 hours.
"BrianInHouston" wrote:
> I am trying to debug an "INSTEAD OF INSERT" trigger on a view in SQL Serve
r
> 2005. I setup a stored procedure to insert to the view, then (in Visual
> Studio) put a stop in the stored procedure. This works fine, until I try
to
> step into the trigger. Then it tells me that no code is available.
> If I try in Visual Studio 2005 to set a breakpoint on this trigger, it won
't
> allow me, saying "A breakpoint could not be inserted at this location".
> This only happens for any trigger on the view. If I try to set a breakpoi
nt
> on a trigger on a table, it works fine.
> Does anyone know a way around this? I really would like to step though th
e
> trigger on the view.|||I don't know the answer to the debugging question, but yes, if you're an
MSDN subscriber and posted this using the account you registered when you
signed up for managed newsgroups, you should get a response within 2
business days. If you don't, the FAQ page points you at
https://support.microsoft.com/commo...d=msdn&pa=msdnw
to contact the folks at MSDN about it.
The first thing to do, however, is to ensure that the alias that you're
posting with is registered properly. To do that, go to
http://msdn.microsoft.com/subscriptions/, sign in, and click the Managed
Newsgroups link.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"BrianInHouston" <BrianInHouston@.discussions.microsoft.com> wrote in message
news:66D6AC1C-BB18-4FC4-B30C-F94D33A441E2@.microsoft.com...[vbcol=seagreen]
> Is anyone going to respond to this? I thought these news groups were
> managed
> and a response could be expected in 48 hours.
> "BrianInHouston" wrote:
>|||Is anyone going to respond to this? I thought these news groups were manage
d
and a response could be expected in 48 hours.
"BrianInHouston" wrote:
> I am trying to debug an "INSTEAD OF INSERT" trigger on a view in SQL Serve
r
> 2005. I setup a stored procedure to insert to the view, then (in Visual
> Studio) put a stop in the stored procedure. This works fine, until I try
to
> step into the trigger. Then it tells me that no code is available.
> If I try in Visual Studio 2005 to set a breakpoint on this trigger, it won
't
> allow me, saying "A breakpoint could not be inserted at this location".
> This only happens for any trigger on the view. If I try to set a breakpoi
nt
> on a trigger on a table, it works fine.
> Does anyone know a way around this? I really would like to step though th
e
> trigger on the view.|||I don't know the answer to the debugging question, but yes, if you're an
MSDN subscriber and posted this using the account you registered when you
signed up for managed newsgroups, you should get a response within 2
business days. If you don't, the FAQ page points you at
https://support.microsoft.com/commo...d=msdn&pa=msdnw
to contact the folks at MSDN about it.
The first thing to do, however, is to ensure that the alias that you're
posting with is registered properly. To do that, go to
http://msdn.microsoft.com/subscriptions/, sign in, and click the Managed
Newsgroups link.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"BrianInHouston" <BrianInHouston@.discussions.microsoft.com> wrote in message
news:66D6AC1C-BB18-4FC4-B30C-F94D33A441E2@.microsoft.com...[vbcol=seagreen]
> Is anyone going to respond to this? I thought these news groups were
> managed
> and a response could be expected in 48 hours.
> "BrianInHouston" wrote:
>
2005. I setup a stored procedure to insert to the view, then (in Visual
Studio) put a stop in the stored procedure. This works fine, until I try to
step into the trigger. Then it tells me that no code is available.
If I try in Visual Studio 2005 to set a breakpoint on this trigger, it won't
allow me, saying "A breakpoint could not be inserted at this location".
This only happens for any trigger on the view. If I try to set a breakpoint
on a trigger on a table, it works fine.
Does anyone know a way around this? I really would like to step though the
trigger on the view.Is anyone going to respond to this? I thought these news groups were manage
d
and a response could be expected in 48 hours.
"BrianInHouston" wrote:
> I am trying to debug an "INSTEAD OF INSERT" trigger on a view in SQL Serve
r
> 2005. I setup a stored procedure to insert to the view, then (in Visual
> Studio) put a stop in the stored procedure. This works fine, until I try
to
> step into the trigger. Then it tells me that no code is available.
> If I try in Visual Studio 2005 to set a breakpoint on this trigger, it won
't
> allow me, saying "A breakpoint could not be inserted at this location".
> This only happens for any trigger on the view. If I try to set a breakpoi
nt
> on a trigger on a table, it works fine.
> Does anyone know a way around this? I really would like to step though th
e
> trigger on the view.|||I don't know the answer to the debugging question, but yes, if you're an
MSDN subscriber and posted this using the account you registered when you
signed up for managed newsgroups, you should get a response within 2
business days. If you don't, the FAQ page points you at
https://support.microsoft.com/commo...d=msdn&pa=msdnw
to contact the folks at MSDN about it.
The first thing to do, however, is to ensure that the alias that you're
posting with is registered properly. To do that, go to
http://msdn.microsoft.com/subscriptions/, sign in, and click the Managed
Newsgroups link.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"BrianInHouston" <BrianInHouston@.discussions.microsoft.com> wrote in message
news:66D6AC1C-BB18-4FC4-B30C-F94D33A441E2@.microsoft.com...[vbcol=seagreen]
> Is anyone going to respond to this? I thought these news groups were
> managed
> and a response could be expected in 48 hours.
> "BrianInHouston" wrote:
>|||Is anyone going to respond to this? I thought these news groups were manage
d
and a response could be expected in 48 hours.
"BrianInHouston" wrote:
> I am trying to debug an "INSTEAD OF INSERT" trigger on a view in SQL Serve
r
> 2005. I setup a stored procedure to insert to the view, then (in Visual
> Studio) put a stop in the stored procedure. This works fine, until I try
to
> step into the trigger. Then it tells me that no code is available.
> If I try in Visual Studio 2005 to set a breakpoint on this trigger, it won
't
> allow me, saying "A breakpoint could not be inserted at this location".
> This only happens for any trigger on the view. If I try to set a breakpoi
nt
> on a trigger on a table, it works fine.
> Does anyone know a way around this? I really would like to step though th
e
> trigger on the view.|||I don't know the answer to the debugging question, but yes, if you're an
MSDN subscriber and posted this using the account you registered when you
signed up for managed newsgroups, you should get a response within 2
business days. If you don't, the FAQ page points you at
https://support.microsoft.com/commo...d=msdn&pa=msdnw
to contact the folks at MSDN about it.
The first thing to do, however, is to ensure that the alias that you're
posting with is registered properly. To do that, go to
http://msdn.microsoft.com/subscriptions/, sign in, and click the Managed
Newsgroups link.
Sincerely,
Stephen Dybing
This posting is provided "AS IS" with no warranties, and confers no rights.
"BrianInHouston" <BrianInHouston@.discussions.microsoft.com> wrote in message
news:66D6AC1C-BB18-4FC4-B30C-F94D33A441E2@.microsoft.com...[vbcol=seagreen]
> Is anyone going to respond to this? I thought these news groups were
> managed
> and a response could be expected in 48 hours.
> "BrianInHouston" wrote:
>
Friday, February 24, 2012
Debugging problem
HI,
Running debugger on the server works like a charm, however, when my
developers try to doc the same thing from ther
desktop (with everything setup correctly), thety get the following error
--
Server: Msg 504, Level 16, State 1, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
on myserver (Error = 0x800706ba).
Ensure that client-side components, such as SQLDBREG.EXE, are installed and
registered on W02875.
Debugging disabled for connection 67.
---
Any idea
ThanksHi
Have you checked out
http://support.microsoft.com/defaul...b;en-us;817178,
http://support.microsoft.com/defaul...kb;en-us;839280 or
http://msdn.microsoft.com/library/d...
ols_5cfm.asp?
John
"SalamElias" wrote:
> HI,
> Running debugger on the server works like a charm, however, when my
> developers try to doc the same thing from ther
> desktop (with everything setup correctly), thety get the following error
> --
> Server: Msg 504, Level 16, State 1, Procedure sp_sdidebug, Line 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
> on myserver (Error = 0x800706ba).
> Ensure that client-side components, such as SQLDBREG.EXE, are installed an
d
> registered on W02875.
> Debugging disabled for connection 67.
> ---
> Any idea
> Thanks
Running debugger on the server works like a charm, however, when my
developers try to doc the same thing from ther
desktop (with everything setup correctly), thety get the following error
--
Server: Msg 504, Level 16, State 1, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
on myserver (Error = 0x800706ba).
Ensure that client-side components, such as SQLDBREG.EXE, are installed and
registered on W02875.
Debugging disabled for connection 67.
---
Any idea
ThanksHi
Have you checked out
http://support.microsoft.com/defaul...b;en-us;817178,
http://support.microsoft.com/defaul...kb;en-us;839280 or
http://msdn.microsoft.com/library/d...
ols_5cfm.asp?
John
"SalamElias" wrote:
> HI,
> Running debugger on the server works like a charm, however, when my
> developers try to doc the same thing from ther
> desktop (with everything setup correctly), thety get the following error
> --
> Server: Msg 504, Level 16, State 1, Procedure sp_sdidebug, Line 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Unable to connect to debugger
> on myserver (Error = 0x800706ba).
> Ensure that client-side components, such as SQLDBREG.EXE, are installed an
d
> registered on W02875.
> Debugging disabled for connection 67.
> ---
> Any idea
> Thanks
Friday, February 17, 2012
Debugger Interface Problem in QA
Hello,
We've setup SQL Debugging on our server, but when I try and test in Query
Analyzer on the server I get the following error:
"The debugger interface is not installed. Please re-run setup, select "add
components to your existing installation' and make sure you select
'Development tools'\'Debugger Interface'."
However, this is already installed when I run setup. I am running SQL SP3,
and noticed some articles about that, but they didn't seem to apply to my
specific problem. I get the same error whether through terminal services or
at the console.
We're having a lot of problems making this work, if anyone can assist I'd
greatly appreciate.
Regards,
Derek
I'm seeing the same issue, did you ever get a resolution?
Ron
"Derek" wrote:
> Hello,
> We've setup SQL Debugging on our server, but when I try and test in Query
> Analyzer on the server I get the following error:
> "The debugger interface is not installed. Please re-run setup, select "add
> components to your existing installation' and make sure you select
> 'Development tools'\'Debugger Interface'."
> However, this is already installed when I run setup. I am running SQL SP3,
> and noticed some articles about that, but they didn't seem to apply to my
> specific problem. I get the same error whether through terminal services or
> at the console.
> We're having a lot of problems making this work, if anyone can assist I'd
> greatly appreciate.
> Regards,
> Derek
>
>
We've setup SQL Debugging on our server, but when I try and test in Query
Analyzer on the server I get the following error:
"The debugger interface is not installed. Please re-run setup, select "add
components to your existing installation' and make sure you select
'Development tools'\'Debugger Interface'."
However, this is already installed when I run setup. I am running SQL SP3,
and noticed some articles about that, but they didn't seem to apply to my
specific problem. I get the same error whether through terminal services or
at the console.
We're having a lot of problems making this work, if anyone can assist I'd
greatly appreciate.
Regards,
Derek
I'm seeing the same issue, did you ever get a resolution?
Ron
"Derek" wrote:
> Hello,
> We've setup SQL Debugging on our server, but when I try and test in Query
> Analyzer on the server I get the following error:
> "The debugger interface is not installed. Please re-run setup, select "add
> components to your existing installation' and make sure you select
> 'Development tools'\'Debugger Interface'."
> However, this is already installed when I run setup. I am running SQL SP3,
> and noticed some articles about that, but they didn't seem to apply to my
> specific problem. I get the same error whether through terminal services or
> at the console.
> We're having a lot of problems making this work, if anyone can assist I'd
> greatly appreciate.
> Regards,
> Derek
>
>
Debugger Interface Problem in QA
Hello,
We've setup SQL Debugging on our server, but when I try and test in Query
Analyzer on the server I get the following error:
"The debugger interface is not installed. Please re-run setup, select "add
components to your existing installation' and make sure you select
'Development tools'\'Debugger Interface'."
However, this is already installed when I run setup. I am running SQL SP3,
and noticed some articles about that, but they didn't seem to apply to my
specific problem. I get the same error whether through terminal services or
at the console.
We're having a lot of problems making this work, if anyone can assist I'd
greatly appreciate.
Regards,
DerekI'm seeing the same issue, did you ever get a resolution?
Ron
"Derek" wrote:
> Hello,
> We've setup SQL Debugging on our server, but when I try and test in Query
> Analyzer on the server I get the following error:
> "The debugger interface is not installed. Please re-run setup, select "add
> components to your existing installation' and make sure you select
> 'Development tools'\'Debugger Interface'."
> However, this is already installed when I run setup. I am running SQL SP3,
> and noticed some articles about that, but they didn't seem to apply to my
> specific problem. I get the same error whether through terminal services or
> at the console.
> We're having a lot of problems making this work, if anyone can assist I'd
> greatly appreciate.
> Regards,
> Derek
>
>
We've setup SQL Debugging on our server, but when I try and test in Query
Analyzer on the server I get the following error:
"The debugger interface is not installed. Please re-run setup, select "add
components to your existing installation' and make sure you select
'Development tools'\'Debugger Interface'."
However, this is already installed when I run setup. I am running SQL SP3,
and noticed some articles about that, but they didn't seem to apply to my
specific problem. I get the same error whether through terminal services or
at the console.
We're having a lot of problems making this work, if anyone can assist I'd
greatly appreciate.
Regards,
DerekI'm seeing the same issue, did you ever get a resolution?
Ron
"Derek" wrote:
> Hello,
> We've setup SQL Debugging on our server, but when I try and test in Query
> Analyzer on the server I get the following error:
> "The debugger interface is not installed. Please re-run setup, select "add
> components to your existing installation' and make sure you select
> 'Development tools'\'Debugger Interface'."
> However, this is already installed when I run setup. I am running SQL SP3,
> and noticed some articles about that, but they didn't seem to apply to my
> specific problem. I get the same error whether through terminal services or
> at the console.
> We're having a lot of problems making this work, if anyone can assist I'd
> greatly appreciate.
> Regards,
> Derek
>
>
debugger interface
Help,
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
debugger interface
Help,
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
debugger interface
Help,
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
MarcIt sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
debugger interface
Help,
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
Marc
It sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
I used to be able to debug a stored procedure in the query analyser.
But now I get an error indicating that I should re-run setup and add the
debugger interface.
the debugger is installed!!!!
if I take a look at the eventviewer I see following error
DCOM got error "the operation completed successfully" and was unable to
togon , \SQLdebugger in order to run the server.
What can I do to correct this problem and switch debugging on again?
Thanks,
Marc
It sounds like the DCOM permissions may no longer set
correctly. Check the topic in books online: Troubleshooting
the Transact-SQL Debugger
Make sure you follow all the steps, especially those for
DCOMCNFG.EXE
You should also check the following knowledge base article:
INF: T-SQL Debugger Is Turned Off By Default for Earlier
Clients After You Install SQL Server 2000 Service Pack 3
http://support.microsoft.com/?id=328151
-Sue
On Tue, 12 Apr 2005 09:40:48 +0200, "marc" <heev@.msn.com>
wrote:
>Help,
>I used to be able to debug a stored procedure in the query analyser.
>But now I get an error indicating that I should re-run setup and add the
>debugger interface.
>the debugger is installed!!!!
>if I take a look at the eventviewer I see following error
>DCOM got error "the operation completed successfully" and was unable to
>togon , \SQLdebugger in order to run the server.
>What can I do to correct this problem and switch debugging on again?
>Thanks,
>Marc
>
Subscribe to:
Posts (Atom)