Making managed code calls inside SQL Server in context of the client

Dear all,

I am very new to the subject of writing CLR code inside SQL Server, so I apologise if my questions seem naive.

I have a requirement to populate an asp.net 2.0 GridView control with data columns, some of which are directly from a SQL Server 2005 database, but some of which are calculated by calling CLR methods passing the values from the database columns to those methods.

However, the methods I need to call only make sense in the process context of the client web site which is calling the stored procedure which I want to write to return the data columns.

In effect, I want to be able to make a remote procedure call from within the SQL Server CLR code to the methods available in the client process.

Is this possible? If so, could someone please refer me to an example of how to do it.

If it can be done, it opens up lots of very cool possibilities!

Thanks.

It's a much cleaner design if you can explicitly pass the client context information to the server-side CLR code rather than RPC back to the client. While you can do anything you want if you register the assembly as unsafe, I don't recommend that approach. It's better for both security and performance reasons to keep server-side processing on the server itself as much as possible.

|||

Dear BonnieFe,

Thanks for your suggestion. It would be a much cleaner design, if it was possible. Unfortunately, the data I need back changes for every row in the returned data, since it is obtained by passing a value from a returned data column to a method which has to be called in the context of the calling process.

I have now solved the problem by calling a web service in the calling web site from the CLR code inside SQL Server 2005. This seems to work fine, although it is bound to be slower than it would be if it used RPC back through the SQL connection.

Make Text File as DataSource in Crystal Report 10

Dear all,

We have Crystal Report 10.
And we want to make a text file (with column separator : | ) as a data source for the crystal report 10.
We check available datasource but we can not find suitable way.
And we do not see any option for text file in ODBC.

Once we were successful but it reads the whole row without splitting it into columns based on "|" sign.

And we do not want to use VB programming.

Pls help.

Thanks
hendysearch here
http://support.businessobjects.com|||You can try creating an ODBC connection to the text file with the text driver. I don't know how successful it will be, but you could try.

Make Table Query

Dear Sir/Madam,

I want to create a replica of another table with all the constraints except primary key.

when i tried the command

SELECT * INTO vch1 FROM Voucher

none of the constraints like DEFAULT, NOT NULL are defined in the new table.

pl. guide me.

with regards

wilfi

Hi Wilfi,

not sure if this is what you are looking for. In SQL 2005 if you right click the table in SSMS then select Script Table As, then CREATE To you can script the table to a new query window. This will provide all the SQL required to create the table as well as all constraints. You can then simply remove the primary key once the table is created.

Hope this helps,

Grant|||SELECT ... INTO does NOT transfer any table constraints -it only transfers data to the new table.|||Or you can just remove the primary key constraint from the DDL that you get from the Script Table As command. Generally speaking though, it is a best practice to build your objects from a file so you can maintain the table create in version control. Then you can just use that script to recreate the table.|||

hey why dont u just right click on the table in enterprise manager and select "COPY" option and then paste in in the Query Analyser window u will get all the constraints u can then change the table name and execute

RegarDs,

Jacx

|||

Thank u sir.

Yes I could do it that way. But i thought with the make table query there may be some option to carry the constraints.

thanks a lot.

with regards

wilfi

|||

Dear Jac,

Yes i could do that & i did that at last. First i thought there may be some option in the

make query to carry the constraints.

thank u.

with regards

wilfi

Make a same copy of SQL Server to a new machine

Dear all,
Since my old server's harddisk drive nearly used up all the free
space, I need to copy it from new server. Can I simply copy all the dat and
log files to new server without detach it provided that there're no user
using it and after that I attach them back to new sql server? I'm afraid in
case there're something go wrong in my new server and I can still use the
old server. And how can I transfer my logins to new server? I read some
articles that it may has orphan users if without transferring them. Or if
anyone knows the proper procedures on coping data into new server. Please
help. Thanks
Best Rdgs
EllisSee if this helps: http://vyaskn.tripod.com/moving_sql_server.htm
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:ezwt5MlvEHA.3228@.TK2MSFTNGP12.phx.gbl...
> Dear all,
> Since my old server's harddisk drive nearly used up all the free
> space, I need to copy it from new server. Can I simply copy all the dat
and
> log files to new server without detach it provided that there're no user
> using it and after that I attach them back to new sql server? I'm afraid
in
> case there're something go wrong in my new server and I can still use the
> old server. And how can I transfer my logins to new server? I read some
> articles that it may has orphan users if without transferring them. Or if
> anyone knows the proper procedures on coping data into new server. Please
> help. Thanks
> Best Rdgs
> Ellis
>

Make a same copy of SQL Server to a new machine

Dear all,
Since my old server's harddisk drive nearly used up all the free
space, I need to copy it from new server. Can I simply copy all the dat and
log files to new server without detach it provided that there're no user
using it and after that I attach them back to new sql server? I'm afraid in
case there're something go wrong in my new server and I can still use the
old server. And how can I transfer my logins to new server? I read some
articles that it may has orphan users if without transferring them. Or if
anyone knows the proper procedures on coping data into new server. Please
help. Thanks
Best Rdgs
Ellis
See if this helps: http://vyaskn.tripod.com/moving_sql_server.htm
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:ezwt5MlvEHA.3228@.TK2MSFTNGP12.phx.gbl...
> Dear all,
> Since my old server's harddisk drive nearly used up all the free
> space, I need to copy it from new server. Can I simply copy all the dat
and
> log files to new server without detach it provided that there're no user
> using it and after that I attach them back to new sql server? I'm afraid
in
> case there're something go wrong in my new server and I can still use the
> old server. And how can I transfer my logins to new server? I read some
> articles that it may has orphan users if without transferring them. Or if
> anyone knows the proper procedures on coping data into new server. Please
> help. Thanks
> Best Rdgs
> Ellis
>

Make a same copy of SQL Server to a new machine

Dear all,
Since my old server's harddisk drive nearly used up all the free
space, I need to copy it from new server. Can I simply copy all the dat and
log files to new server without detach it provided that there're no user
using it and after that I attach them back to new sql server? I'm afraid in
case there're something go wrong in my new server and I can still use the
old server. And how can I transfer my logins to new server? I read some
articles that it may has orphan users if without transferring them. Or if
anyone knows the proper procedures on coping data into new server. Please
help. Thanks
Best Rdgs
EllisSee if this helps: http://vyaskn.tripod.com/moving_sql_server.htm
--
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Ellis Yu" <ellis.yu@.transfield.com> wrote in message
news:ezwt5MlvEHA.3228@.TK2MSFTNGP12.phx.gbl...
> Dear all,
> Since my old server's harddisk drive nearly used up all the free
> space, I need to copy it from new server. Can I simply copy all the dat
and
> log files to new server without detach it provided that there're no user
> using it and after that I attach them back to new sql server? I'm afraid
in
> case there're something go wrong in my new server and I can still use the
> old server. And how can I transfer my logins to new server? I read some
> articles that it may has orphan users if without transferring them. Or if
> anyone knows the proper procedures on coping data into new server. Please
> help. Thanks
> Best Rdgs
> Ellis
>

Make (Select All) as default value in parameter

Dear Anyone,
Does anyone know how to Make (Select All) as default value in parameter selection on a multi-select parameter?

thanks,
Joseph

If the valid values list of the multi value parameter is dataset based, you could set the default value of the parameter to the same dataset field value.

-- Robert

|||

We have the hotfix for the (Select All) option applied (after applying SP1).

However, when the users change another parameter filter which cascades to change to the multivalued parameter filter, the (Select All) option is not reapplied. In other words, if new entries show up in the multivalued parameters list, they are not checked by default, so some records will be missed.

What is the best way to force a (Select All) again after the user filters on another dependent parameter filter?

Make (Select All) as default value in parameter

Dear Anyone,
Does anyone know how to Make (Select All) as default value in parameter selection on a multi-select parameter?

thanks,
Joseph

If the valid values list of the multi value parameter is dataset based, you could set the default value of the parameter to the same dataset field value.

-- Robert

|||

We have the hotfix for the (Select All) option applied (after applying SP1).

However, when the users change another parameter filter which cascades to change to the multivalued parameter filter, the (Select All) option is not reapplied. In other words, if new entries show up in the multivalued parameters list, they are not checked by default, so some records will be missed.

What is the best way to force a (Select All) again after the user filters on another dependent parameter filter?

Make (Select All) as default value in parameter

Dear Anyone,
Does anyone know how to Make (Select All) as default value in parameter selection on a multi-select parameter?

thanks,
Joseph

If the valid values list of the multi value parameter is dataset based, you could set the default value of the parameter to the same dataset field value.

-- Robert

|||

We have the hotfix for the (Select All) option applied (after applying SP1).

However, when the users change another parameter filter which cascades to change to the multivalued parameter filter, the (Select All) option is not reapplied. In other words, if new entries show up in the multivalued parameters list, they are not checked by default, so some records will be missed.

What is the best way to force a (Select All) again after the user filters on another dependent parameter filter?

Major SQL Server 2k5 x64 configuration problem

Dear All,
I've just installed two brand new SQL Server servers with Windows 2003
Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
I now need to configure the network protocols for SQL Server on these
machines, but on both machines the SQL Server instances are not showing up in
the "SQL Server 2005 Configuration manager"
On two other x64 SQL Server 2005 servers which we installed last year I see
a total of 5 icons in the "SQL Server 2005 Configuration manager":
- SQL Server 2005 Services
- SQL Server 2005 Network configuration (32-bit)
- SQL Server 2005 Native Client Configuration (32 Bit)
- SQL Server 2005 Network configuration
- SQL Server 2005 Native Client Configuration
but on the two new servers only the first 3 groups are showing up.
Normaly the x64 Instances are listed in the group as "- SQL Server 2005
Network configuration", but this group is not showing up.
On both servers I only have configured a default (non-named) instance.
Does anybody have a clue what can be wrong or have a hint as where to start
searching for a solution?
Because we posted this question earlier and have not received a single
response I've resorted to crossposting to the following groups:
microsoft.public.sqlserver.server
microsoft.public.sqlserver.tools
microsoft.public.sqlserver.security
microsoft.public.sqlserver.setup
Kind regards,
Tom and Nick, Reeleezee
Solved: through security access failure auditing we saw that user "NETWORK
SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
Server\90\Shared\sqlmgmprovider.dll.
This was because we ourselves routinely implemented our security lock-down
policy of denying Read/Execute access to "C:\Program Files" and "C:\Program
Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
through being an authenticated user.
We hadn't suspected such a security issue when running the tool as
administrator but apparently the Configuration Tool asks WMI to enumerate the
SQL Server instances and WMI does this under the NETWORK SERVICE account.
(not so for the 32-bit nodes?)
We have had no other issue whatsoever from applying our lock-down policy. I
hope this gets into the MS knowledge base.
Nick
"Nick" wrote:

> Dear All,
> I've just installed two brand new SQL Server servers with Windows 2003
> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
> I now need to configure the network protocols for SQL Server on these
> machines, but on both machines the SQL Server instances are not showing up in
> the "SQL Server 2005 Configuration manager"
> On two other x64 SQL Server 2005 servers which we installed last year I see
> a total of 5 icons in the "SQL Server 2005 Configuration manager":
> - SQL Server 2005 Services
> - SQL Server 2005 Network configuration (32-bit)
> - SQL Server 2005 Native Client Configuration (32 Bit)
> - SQL Server 2005 Network configuration
> - SQL Server 2005 Native Client Configuration
> but on the two new servers only the first 3 groups are showing up.
> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
> Network configuration", but this group is not showing up.
> On both servers I only have configured a default (non-named) instance.
> Does anybody have a clue what can be wrong or have a hint as where to start
> searching for a solution?
> Because we posted this question earlier and have not received a single
> response I've resorted to crossposting to the following groups:
> microsoft.public.sqlserver.server
> microsoft.public.sqlserver.tools
> microsoft.public.sqlserver.security
> microsoft.public.sqlserver.setup
>
> Kind regards,
> Tom and Nick, Reeleezee
|||File it as a bug on Connect (Connect.microsoft.com) and it will make it to
the dev team. Whether this makes it all the way to KB article is an
entirely different matter.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...[vbcol=seagreen]
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes?)
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:
|||Nick,
Another set of problems may arise if you also locked down WINDOWS\SysWOW64
(the 32-bit stuff) or WINDOWS\System32 (the 64-bit stuff). For example, this
can prevent the appropriate version of cscript from running, should you have
a SQL Agent job with a cscript step. (And the error message will not be
obvious.)
RLF
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...[vbcol=seagreen]
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes?)
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:

Major SQL Server 2k5 x64 configuration problem

Dear All,
I've just installed two brand new SQL Server servers with Windows 2003
Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
I now need to configure the network protocols for SQL Server on these
machines, but on both machines the SQL Server instances are not showing up in
the "SQL Server 2005 Configuration manager"
On two other x64 SQL Server 2005 servers which we installed last year I see
a total of 5 icons in the "SQL Server 2005 Configuration manager":
- SQL Server 2005 Services
- SQL Server 2005 Network configuration (32-bit)
- SQL Server 2005 Native Client Configuration (32 Bit)
- SQL Server 2005 Network configuration
- SQL Server 2005 Native Client Configuration
but on the two new servers only the first 3 groups are showing up.
Normaly the x64 Instances are listed in the group as "- SQL Server 2005
Network configuration", but this group is not showing up.
On both servers I only have configured a default (non-named) instance.
Does anybody have a clue what can be wrong or have a hint as where to start
searching for a solution?
Because we posted this question earlier and have not received a single
response I've resorted to crossposting to the following groups:
microsoft.public.sqlserver.server
microsoft.public.sqlserver.tools
microsoft.public.sqlserver.security
microsoft.public.sqlserver.setup
Kind regards,
Tom and Nick, Reeleezee
Solved: through security access failure auditing we saw that user "NETWORK
SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
Server\90\Shared\sqlmgmprovider.dll.
This was because we ourselves routinely implemented our security lock-down
policy of denying Read/Execute access to "C:\Program Files" and "C:\Program
Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
through being an authenticated user.
We hadn't suspected such a security issue when running the tool as
administrator but apparently the Configuration Tool asks WMI to enumerate the
SQL Server instances and WMI does this under the NETWORK SERVICE account.
(not so for the 32-bit nodes?)
We have had no other issue whatsoever from applying our lock-down policy. I
hope this gets into the MS knowledge base.
Nick
"Nick" wrote:

> Dear All,
> I've just installed two brand new SQL Server servers with Windows 2003
> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
> I now need to configure the network protocols for SQL Server on these
> machines, but on both machines the SQL Server instances are not showing up in
> the "SQL Server 2005 Configuration manager"
> On two other x64 SQL Server 2005 servers which we installed last year I see
> a total of 5 icons in the "SQL Server 2005 Configuration manager":
> - SQL Server 2005 Services
> - SQL Server 2005 Network configuration (32-bit)
> - SQL Server 2005 Native Client Configuration (32 Bit)
> - SQL Server 2005 Network configuration
> - SQL Server 2005 Native Client Configuration
> but on the two new servers only the first 3 groups are showing up.
> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
> Network configuration", but this group is not showing up.
> On both servers I only have configured a default (non-named) instance.
> Does anybody have a clue what can be wrong or have a hint as where to start
> searching for a solution?
> Because we posted this question earlier and have not received a single
> response I've resorted to crossposting to the following groups:
> microsoft.public.sqlserver.server
> microsoft.public.sqlserver.tools
> microsoft.public.sqlserver.security
> microsoft.public.sqlserver.setup
>
> Kind regards,
> Tom and Nick, Reeleezee
|||File it as a bug on Connect (Connect.microsoft.com) and it will make it to
the dev team. Whether this makes it all the way to KB article is an
entirely different matter.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...[vbcol=seagreen]
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes?)
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:
|||Nick,
Another set of problems may arise if you also locked down WINDOWS\SysWOW64
(the 32-bit stuff) or WINDOWS\System32 (the 64-bit stuff). For example, this
can prevent the appropriate version of cscript from running, should you have
a SQL Agent job with a cscript step. (And the error message will not be
obvious.)
RLF
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...[vbcol=seagreen]
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes?)
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:

Major SQL Server 2k5 x64 configuration problem

Dear All,
I've just installed two brand new SQL Server servers with Windows 2003
Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
I now need to configure the network protocols for SQL Server on these
machines, but on both machines the SQL Server instances are not showing up in
the "SQL Server 2005 Configuration manager"
On two other x64 SQL Server 2005 servers which we installed last year I see
a total of 5 icons in the "SQL Server 2005 Configuration manager":
- SQL Server 2005 Services
- SQL Server 2005 Network configuration (32-bit)
- SQL Server 2005 Native Client Configuration (32 Bit)
- SQL Server 2005 Network configuration
- SQL Server 2005 Native Client Configuration
but on the two new servers only the first 3 groups are showing up.
Normaly the x64 Instances are listed in the group as "- SQL Server 2005
Network configuration", but this group is not showing up.
On both servers I only have configured a default (non-named) instance.
Does anybody have a clue what can be wrong or have a hint as where to start
searching for a solution?
Because we posted this question earlier and have not received a single
response I've resorted to crossposting to the following groups:
microsoft.public.sqlserver.server
microsoft.public.sqlserver.tools
microsoft.public.sqlserver.security
microsoft.public.sqlserver.setup
Kind regards,
Tom and Nick, ReeleezeeSolved: through security access failure auditing we saw that user "NETWORK
SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
Server\90\Shared\sqlmgmprovider.dll.
This was because we ourselves routinely implemented our security lock-down
policy of denying Read/Execute access to "C:\Program Files" and "C:\Program
Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
through being an authenticated user.
We hadn't suspected such a security issue when running the tool as
administrator but apparently the Configuration Tool asks WMI to enumerate the
SQL Server instances and WMI does this under the NETWORK SERVICE account.
(not so for the 32-bit nodes')
We have had no other issue whatsoever from applying our lock-down policy. I
hope this gets into the MS knowledge base.
Nick
"Nick" wrote:
> Dear All,
> I've just installed two brand new SQL Server servers with Windows 2003
> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
> I now need to configure the network protocols for SQL Server on these
> machines, but on both machines the SQL Server instances are not showing up in
> the "SQL Server 2005 Configuration manager"
> On two other x64 SQL Server 2005 servers which we installed last year I see
> a total of 5 icons in the "SQL Server 2005 Configuration manager":
> - SQL Server 2005 Services
> - SQL Server 2005 Network configuration (32-bit)
> - SQL Server 2005 Native Client Configuration (32 Bit)
> - SQL Server 2005 Network configuration
> - SQL Server 2005 Native Client Configuration
> but on the two new servers only the first 3 groups are showing up.
> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
> Network configuration", but this group is not showing up.
> On both servers I only have configured a default (non-named) instance.
> Does anybody have a clue what can be wrong or have a hint as where to start
> searching for a solution?
> Because we posted this question earlier and have not received a single
> response I've resorted to crossposting to the following groups:
> microsoft.public.sqlserver.server
> microsoft.public.sqlserver.tools
> microsoft.public.sqlserver.security
> microsoft.public.sqlserver.setup
>
> Kind regards,
> Tom and Nick, Reeleezee|||File it as a bug on Connect (Connect.microsoft.com) and it will make it to
the dev team. Whether this makes it all the way to KB article is an
entirely different matter.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes')
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:
>> Dear All,
>> I've just installed two brand new SQL Server servers with Windows 2003
>> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
>> I now need to configure the network protocols for SQL Server on these
>> machines, but on both machines the SQL Server instances are not showing
>> up in
>> the "SQL Server 2005 Configuration manager"
>> On two other x64 SQL Server 2005 servers which we installed last year I
>> see
>> a total of 5 icons in the "SQL Server 2005 Configuration manager":
>> - SQL Server 2005 Services
>> - SQL Server 2005 Network configuration (32-bit)
>> - SQL Server 2005 Native Client Configuration (32 Bit)
>> - SQL Server 2005 Network configuration
>> - SQL Server 2005 Native Client Configuration
>> but on the two new servers only the first 3 groups are showing up.
>> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
>> Network configuration", but this group is not showing up.
>> On both servers I only have configured a default (non-named) instance.
>> Does anybody have a clue what can be wrong or have a hint as where to
>> start
>> searching for a solution?
>> Because we posted this question earlier and have not received a single
>> response I've resorted to crossposting to the following groups:
>> microsoft.public.sqlserver.server
>> microsoft.public.sqlserver.tools
>> microsoft.public.sqlserver.security
>> microsoft.public.sqlserver.setup
>>
>> Kind regards,
>> Tom and Nick, Reeleezee|||Nick,
Another set of problems may arise if you also locked down WINDOWS\SysWOW64
(the 32-bit stuff) or WINDOWS\System32 (the 64-bit stuff). For example, this
can prevent the appropriate version of cscript from running, should you have
a SQL Agent job with a cscript step. (And the error message will not be
obvious.)
RLF
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes')
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:
>> Dear All,
>> I've just installed two brand new SQL Server servers with Windows 2003
>> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
>> I now need to configure the network protocols for SQL Server on these
>> machines, but on both machines the SQL Server instances are not showing
>> up in
>> the "SQL Server 2005 Configuration manager"
>> On two other x64 SQL Server 2005 servers which we installed last year I
>> see
>> a total of 5 icons in the "SQL Server 2005 Configuration manager":
>> - SQL Server 2005 Services
>> - SQL Server 2005 Network configuration (32-bit)
>> - SQL Server 2005 Native Client Configuration (32 Bit)
>> - SQL Server 2005 Network configuration
>> - SQL Server 2005 Native Client Configuration
>> but on the two new servers only the first 3 groups are showing up.
>> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
>> Network configuration", but this group is not showing up.
>> On both servers I only have configured a default (non-named) instance.
>> Does anybody have a clue what can be wrong or have a hint as where to
>> start
>> searching for a solution?
>> Because we posted this question earlier and have not received a single
>> response I've resorted to crossposting to the following groups:
>> microsoft.public.sqlserver.server
>> microsoft.public.sqlserver.tools
>> microsoft.public.sqlserver.security
>> microsoft.public.sqlserver.setup
>>
>> Kind regards,
>> Tom and Nick, Reeleezee

Major SQL Server 2k5 x64 configuration problem

Dear All,
I've just installed two brand new SQL Server servers with Windows 2003
Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
I now need to configure the network protocols for SQL Server on these
machines, but on both machines the SQL Server instances are not showing up i
n
the "SQL Server 2005 Configuration manager"
On two other x64 SQL Server 2005 servers which we installed last year I see
a total of 5 icons in the "SQL Server 2005 Configuration manager":
- SQL Server 2005 Services
- SQL Server 2005 Network configuration (32-bit)
- SQL Server 2005 Native Client Configuration (32 Bit)
- SQL Server 2005 Network configuration
- SQL Server 2005 Native Client Configuration
but on the two new servers only the first 3 groups are showing up.
Normaly the x64 Instances are listed in the group as "- SQL Server 2005
Network configuration", but this group is not showing up.
On both servers I only have configured a default (non-named) instance.
Does anybody have a clue what can be wrong or have a hint as where to start
searching for a solution?
Because we posted this question earlier and have not received a single
response I've resorted to crossposting to the following groups:
microsoft.public.sqlserver.server
microsoft.public.sqlserver.tools
microsoft.public.sqlserver.security
microsoft.public.sqlserver.setup
Kind regards,
Tom and Nick, ReeleezeeSolved: through security access failure auditing we saw that user "NETWORK
SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
Server\90\Shared\sqlmgmprovider.dll.
This was because we ourselves routinely implemented our security lock-down
policy of denying Read/Execute access to "C:\Program Files" and "C:\Program
Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
through being an authenticated user.
We hadn't suspected such a security issue when running the tool as
administrator but apparently the Configuration Tool asks WMI to enumerate th
e
SQL Server instances and WMI does this under the NETWORK SERVICE account.
(not so for the 32-bit nodes')
We have had no other issue whatsoever from applying our lock-down policy. I
hope this gets into the MS knowledge base.
Nick
"Nick" wrote:

> Dear All,
> I've just installed two brand new SQL Server servers with Windows 2003
> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
> I now need to configure the network protocols for SQL Server on these
> machines, but on both machines the SQL Server instances are not showing up
in
> the "SQL Server 2005 Configuration manager"
> On two other x64 SQL Server 2005 servers which we installed last year I se
e
> a total of 5 icons in the "SQL Server 2005 Configuration manager":
> - SQL Server 2005 Services
> - SQL Server 2005 Network configuration (32-bit)
> - SQL Server 2005 Native Client Configuration (32 Bit)
> - SQL Server 2005 Network configuration
> - SQL Server 2005 Native Client Configuration
> but on the two new servers only the first 3 groups are showing up.
> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
> Network configuration", but this group is not showing up.
> On both servers I only have configured a default (non-named) instance.
> Does anybody have a clue what can be wrong or have a hint as where to star
t
> searching for a solution?
> Because we posted this question earlier and have not received a single
> response I've resorted to crossposting to the following groups:
> microsoft.public.sqlserver.server
> microsoft.public.sqlserver.tools
> microsoft.public.sqlserver.security
> microsoft.public.sqlserver.setup
>
> Kind regards,
> Tom and Nick, Reeleezee|||File it as a bug on Connect (Connect.microsoft.com) and it will make it to
the dev team. Whether this makes it all the way to KB article is an
entirely different matter.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...[vbcol=seagreen]
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes')
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:
>|||Nick,
Another set of problems may arise if you also locked down WINDOWS\SysWOW64
(the 32-bit stuff) or WINDOWS\System32 (the 64-bit stuff). For example, this
can prevent the appropriate version of cscript from running, should you have
a SQL Agent job with a cscript step. (And the error message will not be
obvious.)
RLF
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...[vbcol=seagreen]
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes')
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:
>

Maintenance Planner Question

Dear All,
I am sorry if this is a silly question but is it possible to run a database
maintenance plan to backup a database to a none fixed hard disk, e.g. a
network share. I have tried running the wizard and at the "Setup Backup Disk
Directory", I only see the fixed hard disk drive (ie C-drive).
I am totally confused. Why do I not see the network share drives. I am using
SQL Server 2000 and Windows XP Professional. I do not have admin rights to
the network but have admin rights to the local machine. Is it to do with the
rights of the logged on user?
As a user I see an H-drive but I do not see it when opening up the wizard.
Thanks for any advice offered.
AlastairType in the UNC name. Make sure that the SQL Server Service account has perm
issions on the share.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote i
n message
news:4B0F083D-6B6E-4D19-BC1C-2D01DD9F3010@.microsoft.com...
> Dear All,
> I am sorry if this is a silly question but is it possible to run a databas
e
> maintenance plan to backup a database to a none fixed hard disk, e.g. a
> network share. I have tried running the wizard and at the "Setup Backup Di
sk
> Directory", I only see the fixed hard disk drive (ie C-drive).
> I am totally confused. Why do I not see the network share drives. I am usi
ng
> SQL Server 2000 and Windows XP Professional. I do not have admin rights to
> the network but have admin rights to the local machine. Is it to do with t
he
> rights of the logged on user?
> As a user I see an H-drive but I do not see it when opening up the wizard.
> Thanks for any advice offered.
> Alastair|||Thanks Tobor for the quick reply.
I am a newcomer to SQL Server and I understand the reference to UNC but I
don't understand "SQL Server Service account has permissions on the share".
Can you please expand upon this or point me to BOL that explains this?
Thanks again and I appreciate your help.
"Tibor Karaszi" wrote:

> Type in the UNC name. Make sure that the SQL Server Service account has pe
rmissions on the share.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote
in message
> news:4B0F083D-6B6E-4D19-BC1C-2D01DD9F3010@.microsoft.com...
>
>|||If you login to the machine using the same Windows account as the SQL Server
service is using (ask a
Windows/Network person if that doesn't make sense), you should be able to wr
ite to the share.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote i
n message
news:54E0F4EC-8BCF-4B33-B022-D4E2B281A315@.microsoft.com...[vbcol=seagreen]
> Thanks Tobor for the quick reply.
> I am a newcomer to SQL Server and I understand the reference to UNC but I
> don't understand "SQL Server Service account has permissions on the share"
.
> Can you please expand upon this or point me to BOL that explains this?
> Thanks again and I appreciate your help.
> "Tibor Karaszi" wrote:
>|||Also see: http://support.microsoft.com/defaul...kb;en-us;555128
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message
news:us1SB417FHA.4076@.tk2msftngp13.phx.gbl...
> If you login to the machine using the same Windows account as the SQL Serv
er service is using (ask
> a Windows/Network person if that doesn't make sense), you should be able t
o write to the share.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote
in message
> news:54E0F4EC-8BCF-4B33-B022-D4E2B281A315@.microsoft.com...
>|||Tibor,
I understand what you mean and I will check with our network guys because I
don't know how to check what credentials the SQL Service is logging in as.
Thanks again.
Alastair
"Tibor Karaszi" wrote:

> Also see: http://support.microsoft.com/defaul...kb;en-us;555128
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n message
> news:us1SB417FHA.4076@.tk2msftngp13.phx.gbl...
>
>|||You can check at the service level or in Enterprise Manager.
Several ways to get to services...
a. Control Panel | Administration Tools | Services
b. Right-click My Computer | Manage, expand Services and Applications and
click Services.
c. Start menu | Administrative Tools | Services.
You need to check these two services: MSSQLSERVER and SQLSERVERAGENT.
Double-click the service.
Click on the log-on tab.
Change/confirm the credentials.
Note: If you have multiple instances of SQL Server installed, EACH instance
has it's own services and therefore has it's own property settings. The
default instance is always "MSSQLSERVER and SQLSERVERAGENT". A named
instance of Joe would be "MSSQL$Joe and SQLAgent$Joe".
In Enterprise Manager, right-click the server object (i.e. (LOCAL)) and
select properties. (Not to be confused with Edit SQL Server Registration
Properties.) For SQL Agent, expand the Management folder, right-click SQL
Server Agent, choose properites.
BTW, the SQL Server Agent needs to be running in order for a database
maintenance plan or a job to execute. And, you cannot use "Local System
Account" because the local system account is not allowed to access the
network. I'm assuming you have a domain and will therefore need a domain
user account for this purpose. Best practices would have you setup a
separate domain user account (i.e. _sql, _joesqlserver, etc.) and apply only
the permissions necessary for SQL Server to do it's work. If you have
multiple instances of SQL Server with different security needs, it would bes
t
to treat each instance or logical group of SQL Servers and apply a separate
user account. For example, if production uses "_sqlserver", you might not
want to use that domain user account for testing as it would give you write
access to production folders, etc. Something to think about.
Hope this helps,
Joe
"Alastair MacFarlane" wrote:
[vbcol=seagreen]
> Tibor,
> I understand what you mean and I will check with our network guys because
I
> don't know how to check what credentials the SQL Service is logging in as.
> Thanks again.
> Alastair
> "Tibor Karaszi" wrote:
>|||To me, it ooks like SQL Server 2000 is installed on a Windows XP
professional PC. If this is the case, then SQL Server service will be runnin
g
as Local System account, and this local system account won't be able to
write to your network drive(H). If you are using a domain account, for
example, something like (Domain\AMacFarlane) to logon to this Windows XP
professional PC and you have Administrator privilages on this PC, try to
change the SQL Server and SQL Server Agent services "Log on as" to your
account (Domain\AMacFarlane) and I believe this will allow you to write to
your network drive(which is mapped to H). You may have to use the UNC name a
s
mentioned before.
"Joe from WI" wrote:
[vbcol=seagreen]
> You can check at the service level or in Enterprise Manager.
> Several ways to get to services...
> a. Control Panel | Administration Tools | Services
> b. Right-click My Computer | Manage, expand Services and Applications and
> click Services.
> c. Start menu | Administrative Tools | Services.
> You need to check these two services: MSSQLSERVER and SQLSERVERAGENT.
> Double-click the service.
> Click on the log-on tab.
> Change/confirm the credentials.
> Note: If you have multiple instances of SQL Server installed, EACH instanc
e
> has it's own services and therefore has it's own property settings. The
> default instance is always "MSSQLSERVER and SQLSERVERAGENT". A named
> instance of Joe would be "MSSQL$Joe and SQLAgent$Joe".
> In Enterprise Manager, right-click the server object (i.e. (LOCAL)) and
> select properties. (Not to be confused with Edit SQL Server Registration
> Properties.) For SQL Agent, expand the Management folder, right-click SQL
> Server Agent, choose properites.
> BTW, the SQL Server Agent needs to be running in order for a database
> maintenance plan or a job to execute. And, you cannot use "Local System
> Account" because the local system account is not allowed to access the
> network. I'm assuming you have a domain and will therefore need a domain
> user account for this purpose. Best practices would have you setup a
> separate domain user account (i.e. _sql, _joesqlserver, etc.) and apply on
ly
> the permissions necessary for SQL Server to do it's work. If you have
> multiple instances of SQL Server with different security needs, it would b
est
> to treat each instance or logical group of SQL Servers and apply a separat
e
> user account. For example, if production uses "_sqlserver", you might not
> want to use that domain user account for testing as it would give you writ
e
> access to production folders, etc. Something to think about.
> Hope this helps,
> Joe
> "Alastair MacFarlane" wrote:
>|||> To me, it ooks like SQL Server 2000 is installed on a Windows XP
> professional PC. If this is the case, then SQL Server service will be runn
ing
> as Local System account,
The OS that SQL Server is installed on does not affect the service account c
hosen. The SQL Server
install program gives you the same options to select service account regardl
ess of the OS you use.

> If you are using a domain account, for
> example, something like (Domain\AMacFarlane) to logon to this Windows XP
> professional PC and you have Administrator privilages on this PC, try to
> change the SQL Server and SQL Server Agent services "Log on as" to your
> account (Domain\AMacFarlane) and I believe this will allow you to write to
> your network drive(which is mapped to H).
Possibly, but only if you first login interactively using that account and m
ap the drive. Mapped
drives are per used in Windows. Hence the recommendation to use UNC naming.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"RV" <RV@.discussions.microsoft.com> wrote in message
news:D0B7C6B9-9AB9-4267-988D-6D79626ECE4C@.microsoft.com...[vbcol=seagreen]
> To me, it ooks like SQL Server 2000 is installed on a Windows XP
> professional PC. If this is the case, then SQL Server service will be runn
ing
> as Local System account, and this local system account won't be able to
> write to your network drive(H). If you are using a domain account, for
> example, something like (Domain\AMacFarlane) to logon to this Windows XP
> professional PC and you have Administrator privilages on this PC, try to
> change the SQL Server and SQL Server Agent services "Log on as" to your
> account (Domain\AMacFarlane) and I believe this will allow you to write to
> your network drive(which is mapped to H). You may have to use the UNC name
as
> mentioned before.
> "Joe from WI" wrote:
>

Maintenance Planner Question

Dear All,
I am sorry if this is a silly question but is it possible to run a database
maintenance plan to backup a database to a none fixed hard disk, e.g. a
network share. I have tried running the wizard and at the "Setup Backup Disk
Directory", I only see the fixed hard disk drive (ie C-drive).
I am totally confused. Why do I not see the network share drives. I am using
SQL Server 2000 and Windows XP Professional. I do not have admin rights to
the network but have admin rights to the local machine. Is it to do with the
rights of the logged on user?
As a user I see an H-drive but I do not see it when opening up the wizard.
Thanks for any advice offered.
Alastair
Type in the UNC name. Make sure that the SQL Server Service account has permissions on the share.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
news:4B0F083D-6B6E-4D19-BC1C-2D01DD9F3010@.microsoft.com...
> Dear All,
> I am sorry if this is a silly question but is it possible to run a database
> maintenance plan to backup a database to a none fixed hard disk, e.g. a
> network share. I have tried running the wizard and at the "Setup Backup Disk
> Directory", I only see the fixed hard disk drive (ie C-drive).
> I am totally confused. Why do I not see the network share drives. I am using
> SQL Server 2000 and Windows XP Professional. I do not have admin rights to
> the network but have admin rights to the local machine. Is it to do with the
> rights of the logged on user?
> As a user I see an H-drive but I do not see it when opening up the wizard.
> Thanks for any advice offered.
> Alastair
|||Thanks Tobor for the quick reply.
I am a newcomer to SQL Server and I understand the reference to UNC but I
don't understand "SQL Server Service account has permissions on the share".
Can you please expand upon this or point me to BOL that explains this?
Thanks again and I appreciate your help.
"Tibor Karaszi" wrote:

> Type in the UNC name. Make sure that the SQL Server Service account has permissions on the share.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
> news:4B0F083D-6B6E-4D19-BC1C-2D01DD9F3010@.microsoft.com...
>
>
|||If you login to the machine using the same Windows account as the SQL Server service is using (ask a
Windows/Network person if that doesn't make sense), you should be able to write to the share.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
news:54E0F4EC-8BCF-4B33-B022-D4E2B281A315@.microsoft.com...[vbcol=seagreen]
> Thanks Tobor for the quick reply.
> I am a newcomer to SQL Server and I understand the reference to UNC but I
> don't understand "SQL Server Service account has permissions on the share".
> Can you please expand upon this or point me to BOL that explains this?
> Thanks again and I appreciate your help.
> "Tibor Karaszi" wrote:
|||Also see: http://support.microsoft.com/default...b;en-us;555128
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
news:us1SB417FHA.4076@.tk2msftngp13.phx.gbl...
> If you login to the machine using the same Windows account as the SQL Server service is using (ask
> a Windows/Network person if that doesn't make sense), you should be able to write to the share.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
> news:54E0F4EC-8BCF-4B33-B022-D4E2B281A315@.microsoft.com...
>
|||Tibor,
I understand what you mean and I will check with our network guys because I
don't know how to check what credentials the SQL Service is logging in as.
Thanks again.
Alastair
"Tibor Karaszi" wrote:

> Also see: http://support.microsoft.com/default...b;en-us;555128
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:us1SB417FHA.4076@.tk2msftngp13.phx.gbl...
>
>
|||You can check at the service level or in Enterprise Manager.
Several ways to get to services...
a. Control Panel | Administration Tools | Services
b. Right-click My Computer | Manage, expand Services and Applications and
click Services.
c. Start menu | Administrative Tools | Services.
You need to check these two services: MSSQLSERVER and SQLSERVERAGENT.
Double-click the service.
Click on the log-on tab.
Change/confirm the credentials.
Note: If you have multiple instances of SQL Server installed, EACH instance
has it's own services and therefore has it's own property settings. The
default instance is always "MSSQLSERVER and SQLSERVERAGENT". A named
instance of Joe would be "MSSQL$Joe and SQLAgent$Joe".
In Enterprise Manager, right-click the server object (i.e. (LOCAL)) and
select properties. (Not to be confused with Edit SQL Server Registration
Properties.) For SQL Agent, expand the Management folder, right-click SQL
Server Agent, choose properites.
BTW, the SQL Server Agent needs to be running in order for a database
maintenance plan or a job to execute. And, you cannot use "Local System
Account" because the local system account is not allowed to access the
network. I'm assuming you have a domain and will therefore need a domain
user account for this purpose. Best practices would have you setup a
separate domain user account (i.e. _sql, _joesqlserver, etc.) and apply only
the permissions necessary for SQL Server to do it's work. If you have
multiple instances of SQL Server with different security needs, it would best
to treat each instance or logical group of SQL Servers and apply a separate
user account. For example, if production uses "_sqlserver", you might not
want to use that domain user account for testing as it would give you write
access to production folders, etc. Something to think about.
Hope this helps,
Joe
"Alastair MacFarlane" wrote:
[vbcol=seagreen]
> Tibor,
> I understand what you mean and I will check with our network guys because I
> don't know how to check what credentials the SQL Service is logging in as.
> Thanks again.
> Alastair
> "Tibor Karaszi" wrote:
|||To me, it ooks like SQL Server 2000 is installed on a Windows XP
professional PC. If this is the case, then SQL Server service will be running
as Local System account, and this local system account won't be able to
write to your network drive(H). If you are using a domain account, for
example, something like (Domain\AMacFarlane) to logon to this Windows XP
professional PC and you have Administrator privilages on this PC, try to
change the SQL Server and SQL Server Agent services "Log on as" to your
account (Domain\AMacFarlane) and I believe this will allow you to write to
your network drive(which is mapped to H). You may have to use the UNC name as
mentioned before.
"Joe from WI" wrote:
[vbcol=seagreen]
> You can check at the service level or in Enterprise Manager.
> Several ways to get to services...
> a. Control Panel | Administration Tools | Services
> b. Right-click My Computer | Manage, expand Services and Applications and
> click Services.
> c. Start menu | Administrative Tools | Services.
> You need to check these two services: MSSQLSERVER and SQLSERVERAGENT.
> Double-click the service.
> Click on the log-on tab.
> Change/confirm the credentials.
> Note: If you have multiple instances of SQL Server installed, EACH instance
> has it's own services and therefore has it's own property settings. The
> default instance is always "MSSQLSERVER and SQLSERVERAGENT". A named
> instance of Joe would be "MSSQL$Joe and SQLAgent$Joe".
> In Enterprise Manager, right-click the server object (i.e. (LOCAL)) and
> select properties. (Not to be confused with Edit SQL Server Registration
> Properties.) For SQL Agent, expand the Management folder, right-click SQL
> Server Agent, choose properites.
> BTW, the SQL Server Agent needs to be running in order for a database
> maintenance plan or a job to execute. And, you cannot use "Local System
> Account" because the local system account is not allowed to access the
> network. I'm assuming you have a domain and will therefore need a domain
> user account for this purpose. Best practices would have you setup a
> separate domain user account (i.e. _sql, _joesqlserver, etc.) and apply only
> the permissions necessary for SQL Server to do it's work. If you have
> multiple instances of SQL Server with different security needs, it would best
> to treat each instance or logical group of SQL Servers and apply a separate
> user account. For example, if production uses "_sqlserver", you might not
> want to use that domain user account for testing as it would give you write
> access to production folders, etc. Something to think about.
> Hope this helps,
> Joe
> "Alastair MacFarlane" wrote:
|||> To me, it ooks like SQL Server 2000 is installed on a Windows XP
> professional PC. If this is the case, then SQL Server service will be running
> as Local System account,
The OS that SQL Server is installed on does not affect the service account chosen. The SQL Server
install program gives you the same options to select service account regardless of the OS you use.

> If you are using a domain account, for
> example, something like (Domain\AMacFarlane) to logon to this Windows XP
> professional PC and you have Administrator privilages on this PC, try to
> change the SQL Server and SQL Server Agent services "Log on as" to your
> account (Domain\AMacFarlane) and I believe this will allow you to write to
> your network drive(which is mapped to H).
Possibly, but only if you first login interactively using that account and map the drive. Mapped
drives are per used in Windows. Hence the recommendation to use UNC naming.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"RV" <RV@.discussions.microsoft.com> wrote in message
news:D0B7C6B9-9AB9-4267-988D-6D79626ECE4C@.microsoft.com...[vbcol=seagreen]
> To me, it ooks like SQL Server 2000 is installed on a Windows XP
> professional PC. If this is the case, then SQL Server service will be running
> as Local System account, and this local system account won't be able to
> write to your network drive(H). If you are using a domain account, for
> example, something like (Domain\AMacFarlane) to logon to this Windows XP
> professional PC and you have Administrator privilages on this PC, try to
> change the SQL Server and SQL Server Agent services "Log on as" to your
> account (Domain\AMacFarlane) and I believe this will allow you to write to
> your network drive(which is mapped to H). You may have to use the UNC name as
> mentioned before.
> "Joe from WI" wrote:

Maintenance Planner Question

Dear All,
I am sorry if this is a silly question but is it possible to run a database
maintenance plan to backup a database to a none fixed hard disk, e.g. a
network share. I have tried running the wizard and at the "Setup Backup Disk
Directory", I only see the fixed hard disk drive (ie C-drive).
I am totally confused. Why do I not see the network share drives. I am using
SQL Server 2000 and Windows XP Professional. I do not have admin rights to
the network but have admin rights to the local machine. Is it to do with the
rights of the logged on user?
As a user I see an H-drive but I do not see it when opening up the wizard.
Thanks for any advice offered.
AlastairType in the UNC name. Make sure that the SQL Server Service account has permissions on the share.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
news:4B0F083D-6B6E-4D19-BC1C-2D01DD9F3010@.microsoft.com...
> Dear All,
> I am sorry if this is a silly question but is it possible to run a database
> maintenance plan to backup a database to a none fixed hard disk, e.g. a
> network share. I have tried running the wizard and at the "Setup Backup Disk
> Directory", I only see the fixed hard disk drive (ie C-drive).
> I am totally confused. Why do I not see the network share drives. I am using
> SQL Server 2000 and Windows XP Professional. I do not have admin rights to
> the network but have admin rights to the local machine. Is it to do with the
> rights of the logged on user?
> As a user I see an H-drive but I do not see it when opening up the wizard.
> Thanks for any advice offered.
> Alastair|||Thanks Tobor for the quick reply.
I am a newcomer to SQL Server and I understand the reference to UNC but I
don't understand "SQL Server Service account has permissions on the share".
Can you please expand upon this or point me to BOL that explains this?
Thanks again and I appreciate your help.
"Tibor Karaszi" wrote:
> Type in the UNC name. Make sure that the SQL Server Service account has permissions on the share.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
> news:4B0F083D-6B6E-4D19-BC1C-2D01DD9F3010@.microsoft.com...
> > Dear All,
> >
> > I am sorry if this is a silly question but is it possible to run a database
> > maintenance plan to backup a database to a none fixed hard disk, e.g. a
> > network share. I have tried running the wizard and at the "Setup Backup Disk
> > Directory", I only see the fixed hard disk drive (ie C-drive).
> >
> > I am totally confused. Why do I not see the network share drives. I am using
> > SQL Server 2000 and Windows XP Professional. I do not have admin rights to
> > the network but have admin rights to the local machine. Is it to do with the
> > rights of the logged on user?
> >
> > As a user I see an H-drive but I do not see it when opening up the wizard.
> >
> > Thanks for any advice offered.
> >
> > Alastair
>
>|||If you login to the machine using the same Windows account as the SQL Server service is using (ask a
Windows/Network person if that doesn't make sense), you should be able to write to the share.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
news:54E0F4EC-8BCF-4B33-B022-D4E2B281A315@.microsoft.com...
> Thanks Tobor for the quick reply.
> I am a newcomer to SQL Server and I understand the reference to UNC but I
> don't understand "SQL Server Service account has permissions on the share".
> Can you please expand upon this or point me to BOL that explains this?
> Thanks again and I appreciate your help.
> "Tibor Karaszi" wrote:
>> Type in the UNC name. Make sure that the SQL Server Service account has permissions on the share.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
>> news:4B0F083D-6B6E-4D19-BC1C-2D01DD9F3010@.microsoft.com...
>> > Dear All,
>> >
>> > I am sorry if this is a silly question but is it possible to run a database
>> > maintenance plan to backup a database to a none fixed hard disk, e.g. a
>> > network share. I have tried running the wizard and at the "Setup Backup Disk
>> > Directory", I only see the fixed hard disk drive (ie C-drive).
>> >
>> > I am totally confused. Why do I not see the network share drives. I am using
>> > SQL Server 2000 and Windows XP Professional. I do not have admin rights to
>> > the network but have admin rights to the local machine. Is it to do with the
>> > rights of the logged on user?
>> >
>> > As a user I see an H-drive but I do not see it when opening up the wizard.
>> >
>> > Thanks for any advice offered.
>> >
>> > Alastair
>>|||Also see: http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
news:us1SB417FHA.4076@.tk2msftngp13.phx.gbl...
> If you login to the machine using the same Windows account as the SQL Server service is using (ask
> a Windows/Network person if that doesn't make sense), you should be able to write to the share.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
> news:54E0F4EC-8BCF-4B33-B022-D4E2B281A315@.microsoft.com...
>> Thanks Tobor for the quick reply.
>> I am a newcomer to SQL Server and I understand the reference to UNC but I
>> don't understand "SQL Server Service account has permissions on the share".
>> Can you please expand upon this or point me to BOL that explains this?
>> Thanks again and I appreciate your help.
>> "Tibor Karaszi" wrote:
>> Type in the UNC name. Make sure that the SQL Server Service account has permissions on the
>> share.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
>> news:4B0F083D-6B6E-4D19-BC1C-2D01DD9F3010@.microsoft.com...
>> > Dear All,
>> >
>> > I am sorry if this is a silly question but is it possible to run a database
>> > maintenance plan to backup a database to a none fixed hard disk, e.g. a
>> > network share. I have tried running the wizard and at the "Setup Backup Disk
>> > Directory", I only see the fixed hard disk drive (ie C-drive).
>> >
>> > I am totally confused. Why do I not see the network share drives. I am using
>> > SQL Server 2000 and Windows XP Professional. I do not have admin rights to
>> > the network but have admin rights to the local machine. Is it to do with the
>> > rights of the logged on user?
>> >
>> > As a user I see an H-drive but I do not see it when opening up the wizard.
>> >
>> > Thanks for any advice offered.
>> >
>> > Alastair
>>
>|||Tibor,
I understand what you mean and I will check with our network guys because I
don't know how to check what credentials the SQL Service is logging in as.
Thanks again.
Alastair
"Tibor Karaszi" wrote:
> Also see: http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:us1SB417FHA.4076@.tk2msftngp13.phx.gbl...
> > If you login to the machine using the same Windows account as the SQL Server service is using (ask
> > a Windows/Network person if that doesn't make sense), you should be able to write to the share.
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
> > news:54E0F4EC-8BCF-4B33-B022-D4E2B281A315@.microsoft.com...
> >> Thanks Tobor for the quick reply.
> >>
> >> I am a newcomer to SQL Server and I understand the reference to UNC but I
> >> don't understand "SQL Server Service account has permissions on the share".
> >> Can you please expand upon this or point me to BOL that explains this?
> >>
> >> Thanks again and I appreciate your help.
> >>
> >> "Tibor Karaszi" wrote:
> >>
> >> Type in the UNC name. Make sure that the SQL Server Service account has permissions on the
> >> share.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
> >> news:4B0F083D-6B6E-4D19-BC1C-2D01DD9F3010@.microsoft.com...
> >> > Dear All,
> >> >
> >> > I am sorry if this is a silly question but is it possible to run a database
> >> > maintenance plan to backup a database to a none fixed hard disk, e.g. a
> >> > network share. I have tried running the wizard and at the "Setup Backup Disk
> >> > Directory", I only see the fixed hard disk drive (ie C-drive).
> >> >
> >> > I am totally confused. Why do I not see the network share drives. I am using
> >> > SQL Server 2000 and Windows XP Professional. I do not have admin rights to
> >> > the network but have admin rights to the local machine. Is it to do with the
> >> > rights of the logged on user?
> >> >
> >> > As a user I see an H-drive but I do not see it when opening up the wizard.
> >> >
> >> > Thanks for any advice offered.
> >> >
> >> > Alastair
> >>
> >>
> >>
> >
> >
>
>|||You can check at the service level or in Enterprise Manager.
Several ways to get to services...
a. Control Panel | Administration Tools | Services
b. Right-click My Computer | Manage, expand Services and Applications and
click Services.
c. Start menu | Administrative Tools | Services.
You need to check these two services: MSSQLSERVER and SQLSERVERAGENT.
Double-click the service.
Click on the log-on tab.
Change/confirm the credentials.
Note: If you have multiple instances of SQL Server installed, EACH instance
has it's own services and therefore has it's own property settings. The
default instance is always "MSSQLSERVER and SQLSERVERAGENT". A named
instance of Joe would be "MSSQL$Joe and SQLAgent$Joe".
In Enterprise Manager, right-click the server object (i.e. (LOCAL)) and
select properties. (Not to be confused with Edit SQL Server Registration
Properties.) For SQL Agent, expand the Management folder, right-click SQL
Server Agent, choose properites.
BTW, the SQL Server Agent needs to be running in order for a database
maintenance plan or a job to execute. And, you cannot use "Local System
Account" because the local system account is not allowed to access the
network. I'm assuming you have a domain and will therefore need a domain
user account for this purpose. Best practices would have you setup a
separate domain user account (i.e. _sql, _joesqlserver, etc.) and apply only
the permissions necessary for SQL Server to do it's work. If you have
multiple instances of SQL Server with different security needs, it would best
to treat each instance or logical group of SQL Servers and apply a separate
user account. For example, if production uses "_sqlserver", you might not
want to use that domain user account for testing as it would give you write
access to production folders, etc. Something to think about.
Hope this helps,
Joe
"Alastair MacFarlane" wrote:
> Tibor,
> I understand what you mean and I will check with our network guys because I
> don't know how to check what credentials the SQL Service is logging in as.
> Thanks again.
> Alastair
> "Tibor Karaszi" wrote:
> > Also see: http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> >
> >
> > "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> > news:us1SB417FHA.4076@.tk2msftngp13.phx.gbl...
> > > If you login to the machine using the same Windows account as the SQL Server service is using (ask
> > > a Windows/Network person if that doesn't make sense), you should be able to write to the share.
> > >
> > > --
> > > Tibor Karaszi, SQL Server MVP
> > > http://www.karaszi.com/sqlserver/default.asp
> > > http://www.solidqualitylearning.com/
> > >
> > >
> > > "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
> > > news:54E0F4EC-8BCF-4B33-B022-D4E2B281A315@.microsoft.com...
> > >> Thanks Tobor for the quick reply.
> > >>
> > >> I am a newcomer to SQL Server and I understand the reference to UNC but I
> > >> don't understand "SQL Server Service account has permissions on the share".
> > >> Can you please expand upon this or point me to BOL that explains this?
> > >>
> > >> Thanks again and I appreciate your help.
> > >>
> > >> "Tibor Karaszi" wrote:
> > >>
> > >> Type in the UNC name. Make sure that the SQL Server Service account has permissions on the
> > >> share.
> > >>
> > >> --
> > >> Tibor Karaszi, SQL Server MVP
> > >> http://www.karaszi.com/sqlserver/default.asp
> > >> http://www.solidqualitylearning.com/
> > >>
> > >>
> > >> "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
> > >> news:4B0F083D-6B6E-4D19-BC1C-2D01DD9F3010@.microsoft.com...
> > >> > Dear All,
> > >> >
> > >> > I am sorry if this is a silly question but is it possible to run a database
> > >> > maintenance plan to backup a database to a none fixed hard disk, e.g. a
> > >> > network share. I have tried running the wizard and at the "Setup Backup Disk
> > >> > Directory", I only see the fixed hard disk drive (ie C-drive).
> > >> >
> > >> > I am totally confused. Why do I not see the network share drives. I am using
> > >> > SQL Server 2000 and Windows XP Professional. I do not have admin rights to
> > >> > the network but have admin rights to the local machine. Is it to do with the
> > >> > rights of the logged on user?
> > >> >
> > >> > As a user I see an H-drive but I do not see it when opening up the wizard.
> > >> >
> > >> > Thanks for any advice offered.
> > >> >
> > >> > Alastair
> > >>
> > >>
> > >>
> > >
> > >
> >
> >
> >|||To me, it ooks like SQL Server 2000 is installed on a Windows XP
professional PC. If this is the case, then SQL Server service will be running
as Local System account, and this local system account won't be able to
write to your network drive(H). If you are using a domain account, for
example, something like (Domain\AMacFarlane) to logon to this Windows XP
professional PC and you have Administrator privilages on this PC, try to
change the SQL Server and SQL Server Agent services "Log on as" to your
account (Domain\AMacFarlane) and I believe this will allow you to write to
your network drive(which is mapped to H). You may have to use the UNC name as
mentioned before.
"Joe from WI" wrote:
> You can check at the service level or in Enterprise Manager.
> Several ways to get to services...
> a. Control Panel | Administration Tools | Services
> b. Right-click My Computer | Manage, expand Services and Applications and
> click Services.
> c. Start menu | Administrative Tools | Services.
> You need to check these two services: MSSQLSERVER and SQLSERVERAGENT.
> Double-click the service.
> Click on the log-on tab.
> Change/confirm the credentials.
> Note: If you have multiple instances of SQL Server installed, EACH instance
> has it's own services and therefore has it's own property settings. The
> default instance is always "MSSQLSERVER and SQLSERVERAGENT". A named
> instance of Joe would be "MSSQL$Joe and SQLAgent$Joe".
> In Enterprise Manager, right-click the server object (i.e. (LOCAL)) and
> select properties. (Not to be confused with Edit SQL Server Registration
> Properties.) For SQL Agent, expand the Management folder, right-click SQL
> Server Agent, choose properites.
> BTW, the SQL Server Agent needs to be running in order for a database
> maintenance plan or a job to execute. And, you cannot use "Local System
> Account" because the local system account is not allowed to access the
> network. I'm assuming you have a domain and will therefore need a domain
> user account for this purpose. Best practices would have you setup a
> separate domain user account (i.e. _sql, _joesqlserver, etc.) and apply only
> the permissions necessary for SQL Server to do it's work. If you have
> multiple instances of SQL Server with different security needs, it would best
> to treat each instance or logical group of SQL Servers and apply a separate
> user account. For example, if production uses "_sqlserver", you might not
> want to use that domain user account for testing as it would give you write
> access to production folders, etc. Something to think about.
> Hope this helps,
> Joe
> "Alastair MacFarlane" wrote:
> > Tibor,
> >
> > I understand what you mean and I will check with our network guys because I
> > don't know how to check what credentials the SQL Service is logging in as.
> >
> > Thanks again.
> >
> > Alastair
> >
> > "Tibor Karaszi" wrote:
> >
> > > Also see: http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
> > >
> > > --
> > > Tibor Karaszi, SQL Server MVP
> > > http://www.karaszi.com/sqlserver/default.asp
> > > http://www.solidqualitylearning.com/
> > >
> > >
> > > "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> > > news:us1SB417FHA.4076@.tk2msftngp13.phx.gbl...
> > > > If you login to the machine using the same Windows account as the SQL Server service is using (ask
> > > > a Windows/Network person if that doesn't make sense), you should be able to write to the share.
> > > >
> > > > --
> > > > Tibor Karaszi, SQL Server MVP
> > > > http://www.karaszi.com/sqlserver/default.asp
> > > > http://www.solidqualitylearning.com/
> > > >
> > > >
> > > > "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
> > > > news:54E0F4EC-8BCF-4B33-B022-D4E2B281A315@.microsoft.com...
> > > >> Thanks Tobor for the quick reply.
> > > >>
> > > >> I am a newcomer to SQL Server and I understand the reference to UNC but I
> > > >> don't understand "SQL Server Service account has permissions on the share".
> > > >> Can you please expand upon this or point me to BOL that explains this?
> > > >>
> > > >> Thanks again and I appreciate your help.
> > > >>
> > > >> "Tibor Karaszi" wrote:
> > > >>
> > > >> Type in the UNC name. Make sure that the SQL Server Service account has permissions on the
> > > >> share.
> > > >>
> > > >> --
> > > >> Tibor Karaszi, SQL Server MVP
> > > >> http://www.karaszi.com/sqlserver/default.asp
> > > >> http://www.solidqualitylearning.com/
> > > >>
> > > >>
> > > >> "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
> > > >> news:4B0F083D-6B6E-4D19-BC1C-2D01DD9F3010@.microsoft.com...
> > > >> > Dear All,
> > > >> >
> > > >> > I am sorry if this is a silly question but is it possible to run a database
> > > >> > maintenance plan to backup a database to a none fixed hard disk, e.g. a
> > > >> > network share. I have tried running the wizard and at the "Setup Backup Disk
> > > >> > Directory", I only see the fixed hard disk drive (ie C-drive).
> > > >> >
> > > >> > I am totally confused. Why do I not see the network share drives. I am using
> > > >> > SQL Server 2000 and Windows XP Professional. I do not have admin rights to
> > > >> > the network but have admin rights to the local machine. Is it to do with the
> > > >> > rights of the logged on user?
> > > >> >
> > > >> > As a user I see an H-drive but I do not see it when opening up the wizard.
> > > >> >
> > > >> > Thanks for any advice offered.
> > > >> >
> > > >> > Alastair
> > > >>
> > > >>
> > > >>
> > > >
> > > >
> > >
> > >
> > >|||> To me, it ooks like SQL Server 2000 is installed on a Windows XP
> professional PC. If this is the case, then SQL Server service will be running
> as Local System account,
The OS that SQL Server is installed on does not affect the service account chosen. The SQL Server
install program gives you the same options to select service account regardless of the OS you use.
> If you are using a domain account, for
> example, something like (Domain\AMacFarlane) to logon to this Windows XP
> professional PC and you have Administrator privilages on this PC, try to
> change the SQL Server and SQL Server Agent services "Log on as" to your
> account (Domain\AMacFarlane) and I believe this will allow you to write to
> your network drive(which is mapped to H).
Possibly, but only if you first login interactively using that account and map the drive. Mapped
drives are per used in Windows. Hence the recommendation to use UNC naming.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"RV" <RV@.discussions.microsoft.com> wrote in message
news:D0B7C6B9-9AB9-4267-988D-6D79626ECE4C@.microsoft.com...
> To me, it ooks like SQL Server 2000 is installed on a Windows XP
> professional PC. If this is the case, then SQL Server service will be running
> as Local System account, and this local system account won't be able to
> write to your network drive(H). If you are using a domain account, for
> example, something like (Domain\AMacFarlane) to logon to this Windows XP
> professional PC and you have Administrator privilages on this PC, try to
> change the SQL Server and SQL Server Agent services "Log on as" to your
> account (Domain\AMacFarlane) and I believe this will allow you to write to
> your network drive(which is mapped to H). You may have to use the UNC name as
> mentioned before.
> "Joe from WI" wrote:
>> You can check at the service level or in Enterprise Manager.
>> Several ways to get to services...
>> a. Control Panel | Administration Tools | Services
>> b. Right-click My Computer | Manage, expand Services and Applications and
>> click Services.
>> c. Start menu | Administrative Tools | Services.
>> You need to check these two services: MSSQLSERVER and SQLSERVERAGENT.
>> Double-click the service.
>> Click on the log-on tab.
>> Change/confirm the credentials.
>> Note: If you have multiple instances of SQL Server installed, EACH instance
>> has it's own services and therefore has it's own property settings. The
>> default instance is always "MSSQLSERVER and SQLSERVERAGENT". A named
>> instance of Joe would be "MSSQL$Joe and SQLAgent$Joe".
>> In Enterprise Manager, right-click the server object (i.e. (LOCAL)) and
>> select properties. (Not to be confused with Edit SQL Server Registration
>> Properties.) For SQL Agent, expand the Management folder, right-click SQL
>> Server Agent, choose properites.
>> BTW, the SQL Server Agent needs to be running in order for a database
>> maintenance plan or a job to execute. And, you cannot use "Local System
>> Account" because the local system account is not allowed to access the
>> network. I'm assuming you have a domain and will therefore need a domain
>> user account for this purpose. Best practices would have you setup a
>> separate domain user account (i.e. _sql, _joesqlserver, etc.) and apply only
>> the permissions necessary for SQL Server to do it's work. If you have
>> multiple instances of SQL Server with different security needs, it would best
>> to treat each instance or logical group of SQL Servers and apply a separate
>> user account. For example, if production uses "_sqlserver", you might not
>> want to use that domain user account for testing as it would give you write
>> access to production folders, etc. Something to think about.
>> Hope this helps,
>> Joe
>> "Alastair MacFarlane" wrote:
>> > Tibor,
>> >
>> > I understand what you mean and I will check with our network guys because I
>> > don't know how to check what credentials the SQL Service is logging in as.
>> >
>> > Thanks again.
>> >
>> > Alastair
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> > > Also see: http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
>> > >
>> > > --
>> > > Tibor Karaszi, SQL Server MVP
>> > > http://www.karaszi.com/sqlserver/default.asp
>> > > http://www.solidqualitylearning.com/
>> > >
>> > >
>> > > "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> > > news:us1SB417FHA.4076@.tk2msftngp13.phx.gbl...
>> > > > If you login to the machine using the same Windows account as the SQL Server service is
>> > > > using (ask
>> > > > a Windows/Network person if that doesn't make sense), you should be able to write to the
>> > > > share.
>> > > >
>> > > > --
>> > > > Tibor Karaszi, SQL Server MVP
>> > > > http://www.karaszi.com/sqlserver/default.asp
>> > > > http://www.solidqualitylearning.com/
>> > > >
>> > > >
>> > > > "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
>> > > > news:54E0F4EC-8BCF-4B33-B022-D4E2B281A315@.microsoft.com...
>> > > >> Thanks Tobor for the quick reply.
>> > > >>
>> > > >> I am a newcomer to SQL Server and I understand the reference to UNC but I
>> > > >> don't understand "SQL Server Service account has permissions on the share".
>> > > >> Can you please expand upon this or point me to BOL that explains this?
>> > > >>
>> > > >> Thanks again and I appreciate your help.
>> > > >>
>> > > >> "Tibor Karaszi" wrote:
>> > > >>
>> > > >> Type in the UNC name. Make sure that the SQL Server Service account has permissions on
>> > > >> the
>> > > >> share.
>> > > >>
>> > > >> --
>> > > >> Tibor Karaszi, SQL Server MVP
>> > > >> http://www.karaszi.com/sqlserver/default.asp
>> > > >> http://www.solidqualitylearning.com/
>> > > >>
>> > > >>
>> > > >> "Alastair MacFarlane" <AlastairMacFarlane@.discussions.microsoft.com> wrote in message
>> > > >> news:4B0F083D-6B6E-4D19-BC1C-2D01DD9F3010@.microsoft.com...
>> > > >> > Dear All,
>> > > >> >
>> > > >> > I am sorry if this is a silly question but is it possible to run a database
>> > > >> > maintenance plan to backup a database to a none fixed hard disk, e.g. a
>> > > >> > network share. I have tried running the wizard and at the "Setup Backup Disk
>> > > >> > Directory", I only see the fixed hard disk drive (ie C-drive).
>> > > >> >
>> > > >> > I am totally confused. Why do I not see the network share drives. I am using
>> > > >> > SQL Server 2000 and Windows XP Professional. I do not have admin rights to
>> > > >> > the network but have admin rights to the local machine. Is it to do with the
>> > > >> > rights of the logged on user?
>> > > >> >
>> > > >> > As a user I see an H-drive but I do not see it when opening up the wizard.
>> > > >> >
>> > > >> > Thanks for any advice offered.
>> > > >> >
>> > > >> > Alastair
>> > > >>
>> > > >>
>> > > >>
>> > > >
>> > > >
>> > >
>> > >
>> > >