SQL Database locati...
 
Notifications
Clear all

SQL Database location split database and log files

4 Posts
2 Users
0 Reactions
1,884 Views
Posts: 21
Topic starter
(@wupsje)
Eminent Member
Joined: 9 years ago

Hi,

I have a SQL 2016 database server. With a D: drive for SQL data and E: for logs.

Somehow when using default database location it puts the databases on the original default path : C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLDATA.

When I use a fixed path it put both SQL data and log file there.

How would i go about fixing this?

3 Replies
Posts: 1458
Admin
(@trobinson)
Noble Member
Joined: 9 years ago

Hello,

 

You can set the custom db path in the provider settings. Currently you are unable to separate the database from the logs.

 

As far as making fix's yourself you can signup to be a contributor at https://solidcp.com/contributors/become-a-contributor/ which gives you access to the source code and submit fix's you have implemented.

 

Kind regards,

 

Trevor Robinson

Reply
Posts: 21
Topic starter
(@wupsje)
Eminent Member
Joined: 9 years ago

I don't think i'm quite that versed in programming.
Powershell & vbscript mostly

Reply
Posts: 21
Topic starter
(@wupsje)
Eminent Member
Joined: 9 years ago

From what I can tell the default database location is being selected as path where the master DB resides.
Or whatever you override it with.

SQL stores the default data and log path's in the registry. If somehow you could use those as default that would be great.

 

HKEYSoftwareMicrosoftMicrosoft SQL Server#sql version#MSSQLServer

DefaultData

DefaultLog

Reply
Share: