Is it ok for a SQL2K5 TSQL job to use a UNC pointing to a db on same

Microsoft generally recommends against networked db's per
http://support.microsoft.com/kb/304261. Unfortunately, there is a
dispute in our organization and advice from local Microsoft resources
against changing Trace flag 1807 to use UNCs even if the UNC points to
a local db (i.e., dbms, job and db are on the same server). A
Microsoft SQL SME even suggested the use of UNCs makes the local db i/
o go through the server's network stack even though everything is on
the same machine.
Currently, our SQL jobs use mapped drives. In order to for our SQL
jobs to be imported into our Tidal Enterprise Scheduler environment we
have to use UNCs for them to be parsed corrected by Tidal.
Any substantive clarity would be greatly appreciated.I fail to see what you would change the location of the database files (to UNC), where you really
seem to be talking about jobs. Two different things.
I too believe that UNC result in some pass through some network stack. For instance, try starting
SQL Server using LocalSystem and do some xp_cmdshell or backup to an UNC, even if local. ... from
memory, I should add.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
<kkekoa@.gmail.com> wrote in message
news:ec667a6f-3cb1-4d7b-96f8-79472c2eac7b@.p69g2000hsa.googlegroups.com...
> Microsoft generally recommends against networked db's per
> http://support.microsoft.com/kb/304261. Unfortunately, there is a
> dispute in our organization and advice from local Microsoft resources
> against changing Trace flag 1807 to use UNCs even if the UNC points to
> a local db (i.e., dbms, job and db are on the same server). A
> Microsoft SQL SME even suggested the use of UNCs makes the local db i/
> o go through the server's network stack even though everything is on
> the same machine.
> Currently, our SQL jobs use mapped drives. In order to for our SQL
> jobs to be imported into our Tidal Enterprise Scheduler environment we
> have to use UNCs for them to be parsed corrected by Tidal.
> Any substantive clarity would be greatly appreciated.|||Jobs should have no direct contact with ANY of the SQL Server database
files, so the question should not come up. The only process that
touches those files is the SQL Server service. When jobs - or
anything else - needs to interact with a database it interacts with
the SQL Server service, and the service does all the work with the
files.
For whatever a job has to do that relates to files UNC paths are fine.
And I agree that there will be another layer of work using a UNC path
rather than the letter of a directly connected drive. I don't believe
there would be any difference between a mapped network drive and a UNC
reference to the same drive.
Roy Harvey
Beacon Falls, CT
On Wed, 30 Jan 2008 00:00:45 -0800 (PST), kkekoa@.gmail.com wrote:
>Microsoft generally recommends against networked db's per
>http://support.microsoft.com/kb/304261. Unfortunately, there is a
>dispute in our organization and advice from local Microsoft resources
>against changing Trace flag 1807 to use UNCs even if the UNC points to
>a local db (i.e., dbms, job and db are on the same server). A
>Microsoft SQL SME even suggested the use of UNCs makes the local db i/
>o go through the server's network stack even though everything is on
>the same machine.
>Currently, our SQL jobs use mapped drives. In order to for our SQL
>jobs to be imported into our Tidal Enterprise Scheduler environment we
>have to use UNCs for them to be parsed corrected by Tidal.
>Any substantive clarity would be greatly appreciated.|||<kkekoa@.gmail.com> wrote in message
news:ec667a6f-3cb1-4d7b-96f8-79472c2eac7b@.p69g2000hsa.googlegroups.com...
> Microsoft generally recommends against networked db's per
> http://support.microsoft.com/kb/304261. Unfortunately, there is a
> dispute in our organization and advice from local Microsoft resources
> against changing Trace flag 1807 to use UNCs even if the UNC points to
> a local db (i.e., dbms, job and db are on the same server). A
> Microsoft SQL SME even suggested the use of UNCs makes the local db i/
> o go through the server's network stack even though everything is on
> the same machine.
I believe that's correct. It would be a very bad idea to use Trace flag 1807
and UNCs for local database files. Why would you want to do that?
> Currently, our SQL jobs use mapped drives. In order to for our SQL
> jobs to be imported into our Tidal Enterprise Scheduler environment we
> have to use UNCs for them to be parsed corrected by Tidal.
>
I don't understand what you mean. Jobs should have nothing to do with where
your databases are located. In fact jobs reside in the MSDB database. Jobs
are processed by the SQL Agent service so they will have access to whatever
drives the agent does - drive letters or UNC. Could you explain a bit more
about what the problem is.
--
David Portas