Creating SQL Server database with data and log file on synology NAS Server -


i need create new database application. planned put data files on nas server (synology 812). tried create database using different paths 2 days nothing worked. @ bottom can see example path n'\\10.1.1.5\fileserver\...

i tried 'n\\10.1.1.5\**volume1\fileserver**\payroll.ldf' because synology admin interface properties dialog shows path fileserver shared directory.

fileserver shared folder. can reach folder file explorer.

\\10.1.1.5\fileserver\ 

and can create new file or folders inside using windows explorer. unluckily create statement not work.

    create database payroll     on     ( name = payroll_dat,        filename = n'\\10.1.1.5\fileserver\payrolldat.mdf',        size = 20mb,        maxsize = 70mb,        filegrowth = 5mb )     log on     ( name = 'payroll_log',        filename = n'\\10.1.1.5\fileserver\payroll.ldf',        size = 10mb,        maxsize = 40mb,        filegrowth = 5mb )     go 

i happy if has solution problem.

thank time.

ferda

sql server doesn't support unc paths default. see kb @ http://support.microsoft.com/kb/304261 - description of support network database files in sql server.

extracts:

microsoft recommends use storage area network (san) or locally attached disk storage of microsoft sql server database files because configuration optimizes sql server performance , reliability. default, use of network database files (stored on networked server or network attached storage [nas]) not enabled sql server.

it can enabled, must ensure hardware meets strict conditions:

however, can configure sql server store database on networked server or nas storage server. servers used purpose must meet sql server requirements data write ordering , write-through guarantees, detailed in "more information" section.

[...]

any failure software or hardware component honor protocol can result in partial or total data loss or corruption in event of system failure.

[...]

microsoft not support sql server networked database files on nas or networked storage servers not meet these write-through , write-order requirements.

performance can heavily compromised:

in simplest form, nas solution uses standard network redirector software stack, standard network interface card (nic), , standard ethernet components. drawback of configuration file i/o processed through network stack , subject bandwidth limitations of network itself. can create performance , data reliability problems, in programs require extremely high levels of file i/o, such sql server. in nas configurations tested microsoft, i/o throughput approximately one-third (1/3) of direct attached storage solution on same server. in same configuration, cpu cost complete i/o through nas device approximately twice of local i/o.

so in summary, if can't gurantee hardware supports these requirements, you're playing fire. might work small test environment, i'd not host live database lest data gets corrupted or performance severely suffers.

to enable, use trace flag 1807 decribed in kb.


Comments

Popular posts from this blog

c# - DetailsView in ASP.Net - How to add another column on the side/add a control in each row? -

javascript - firefox memory leak -

Trying to import CSV file to a SQL Server database using asp.net and c# - can't find what I'm missing -