Re: Installing SQLServer to use UNC path in place of a drive letter

[Guest msnews.microsoft.com]

Re: Installing SQLServer to use UNC path in place of a drive letter

 

"msnews.microsoft.com" <SQL_Help@aaa.com> wrote in message

news:%23YCTnssIJHA.2580@TK2MSFTNGP05.phx.gbl...

> Thanks for the reply, Tibor.

>

> Sorry I missed this. Yes, I had created a test file in the share, while

> logging in as the service account and it worked fine. I will ask this in a

> Windows group. Thanks for your help, Tibor.

>

> "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote

> in message news:e%23ZMhXsIJHA.3644@TK2MSFTNGP05.phx.gbl...

>> CREATE DATABASE code will *always* run as the service account. It doesn't

>> matter who you login as. I suggested that you yourself (while using the

>> service account) create some file. This to see if the service account has

>> the proper permissions. Anyhow, since this is definitely an OS issue, I

>> suggest you ask in an appropriate Windows group, since you are more

>> likely to find experts on such matters there.

>>

>> --

>> Tibor Karaszi, SQL Server MVP

>> http://www.karaszi.com/sqlserver/default.asp

>> http://sqlblog.com/blogs/tibor_karaszi

>>

>>

>> "msnews.microsoft.com" <SQL_Help@aaa.com> wrote in message

>> news:%23dMqKkrIJHA.1304@TK2MSFTNGP02.phx.gbl...

>>> Thanks for the reply, Tibor.

>>>

>>> I had infact ran the CREATE DATABASE command after logging in as the sql

>>> service account. Thats when I encountered the error. I googled for the

>>> error but no good leads there either.

>>>

>>> "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com> wrote

>>> in message news:uIqAY3kIJHA.1160@TK2MSFTNGP04.phx.gbl...

>>>> The error doesn't ring any bells. Seems like an error returned by the

>>>> operating system to SQL Server, so you might want to search wider for

>>>> the OS error text and number (1337). One possible approach to

>>>> troubleshooting is to login interactively as the SQL Server service

>>>> account and see if you can create a file (notepad or whatever). OF

>>>> course, one never know if SQL Server does something different from your

>>>> app when it opens the file so that only gives you partial coverage...

>>>>

>>>> --

>>>> Tibor Karaszi, SQL Server MVP

>>>> http://www.karaszi.com/sqlserver/default.asp

>>>> http://sqlblog.com/blogs/tibor_karaszi

>>>>

>>>>

>>>> "msnews.microsoft.com" <SQL_Help@aaa.com> wrote in message

>>>> news:u5a5iBiIJHA.1304@TK2MSFTNGP02.phx.gbl...

>>>>> Thanks Tibor. This is just a test instance and I am just exploring

>>>>> options. I know that 1807 is a undocumented option.

>>>>>

>>>>> The previous error was because I did not mention -T1807 , instead I

>>>>> just gave T1807. After I gave -T1807, this is the error:

>>>>>

>>>>> Msg 1802, Level 16, State 4, Line 1

>>>>> CREATE DATABASE failed. Some file names listed could not be created.

>>>>> Check related errors.

>>>>> Msg 5123, Level 16, State 1, Line 1

>>>>> CREATE FILE encountered operating system error 1337(The security ID

>>>>> structure is invalid.) while attempting to open or create the physical

>>>>> file ' \\bigserversnas01\sql_use\sqldata.mdf '.

>>>>>

>>>>> Any idea?

>>>>>

>>>>> "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com>

>>>>> wrote in message news:eEuLf3hIJHA.1160@TK2MSFTNGP05.phx.gbl...

>>>>>

>>>>>> Perhaps you didn't add the traceflag for the right instance? The

>>>>>> error message does indeed suggest that the instance is *not* started

>>>>>> with that traceflag.

>>>>>>

>>>>>> I just like to say again that using UNC *is not* recommended!!!

>>>>>>

>>>>>> --

>>>>>> Tibor Karaszi, SQL Server MVP

>>>>>> http://www.karaszi.com/sqlserver/default.asp

>>>>>> http://sqlblog.com/blogs/tibor_karaszi

>>>>>>

>>>>>>

>>>>>> "msnews.microsoft.com" <SQL_Help@aaa.com> wrote in message

>>>>>> news:eFzhDThIJHA.696@TK2MSFTNGP02.phx.gbl...

>>>>>>> Thank you Tibor.

>>>>>>>

>>>>>>> I have installed SQL2005 Dev edition and changed the 'startup

>>>>>>> parameter' as:

>>>>>>> -dC:\Program Files\Microsoft SQL

>>>>>>> Server\MSSQL.1\MSSQL\DATA\master.mdf;-eC:\Program Files\Microsoft

>>>>>>> SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG;-lC:\Program Files\Microsoft

>>>>>>> SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf;T1807

>>>>>>>

>>>>>>> Means, I added Trace flag#1807 as mentioned in the below article.

>>>>>>> Restarted the service. Even then, when I try to CREATE DATABASE with

>>>>>>> mdf in \\bigserversnas01\sql_use\sqldata.mdf , I get the error:

>>>>>>>

>>>>>>> "The file \\bigserversnas01\sql_use\sqldata.mdf is on a network path

>>>>>>> that is not supported for database files."

>>>>>>>

>>>>>>> What am I doing wrong?

>>>>>>>

>>>>>>>

>>>>>>> "Tibor Karaszi" <tibor_please.no.email_karaszi@hotmail.nomail.com>

>>>>>>> wrote in message news:OL%23l6U6HJHA.4600@TK2MSFTNGP06.phx.gbl...

>>>>>>>> SAN is a very different thing from NAS. You probably want to stay

>>>>>>>> away from NAS:

>>>>>>>>

>>>>>>>> http://support.microsoft.com/kb/304261

>>>>>>>>

>>>>>>>> --

>>>>>>>> Tibor Karaszi, SQL Server MVP

>>>>>>>> http://www.karaszi.com/sqlserver/default.asp

>>>>>>>> http://sqlblog.com/blogs/tibor_karaszi

>>>>>>>>

>>>>>>>>

>>>>>>>> "msnews.microsoft.com" <SQL_Help@aaa.com> wrote in message

>>>>>>>> news:e9KjSQ6HJHA.1160@TK2MSFTNGP05.phx.gbl...

>>>>>>>>> Hello all,

>>>>>>>>>

>>>>>>>>> I need to install SQL2005 Dev edition such that it uses the 1TB

>>>>>>>>> space available in a share via SAN, as a drive letter. How can I

>>>>>>>>> install SQLServer such that it uses a UNC path (such as

>>>>>>>>> \\bigserversnas01\sql_use) as a drive letter?

>>>>>>>>>

>>>>>>>>> Has anyone attempted this? Any things to watch out to make sure

>>>>>>>>> that SQL Server play nicely with a storage area network?

>>>>>>>>>

>>>>>>>>>

>>>>>>>>>

>>>>>>>>> Thank you,

>>>>>>>>> SQL_Help

>>>>>>>>>

>>>>>>>>>

>>>>>>>>>

>>>>>>>>

>>>>>>>>

>>>>>>>

>>>>>>>

>>>>>>

>>>>>>

>>>>>

>>>>>

>>>>

>>>>

>>>

>>>

>>

>>

>

>