Skip to main content
Database Administrators

Return to Question

Tweeted twitter.com/#!/StackDBAs/status/626036660120199168
corrected spelling and punctuation, replaced an irrelevant tag
Source Link
Andriy M
Andriy M
  • 23.2k
  • 6
  • 59
  • 103

Why is it bad practisepractice to install SQL-Server Server to the root of a drive

When I install SQL-Server Server into the root of my drive, for example D:\, I get an error when I run a database deployer formfrom a third party piece of software.

But when I move my SQL-Server install Server instance to D:\SQL\ (move it to a folder within the drive) then installation works perfectly.

My question doesn't regard the database deployer but more into the reason why SQL would have an issue with being installed into the root of a drive. Is this bad practisepractice? Why shouldn't I install SQL-Server Server to the root of my drive?

Why is it bad practise to install SQL-Server to root of a drive

When I install SQL-Server into the root of my drive, for example D:\ I get an error when I run a database deployer form a third party piece of software.

But when I move my SQL-Server install to D:\SQL\ (move it to a folder within the drive) then installation works perfectly.

My question doesn't regard the database deployer but more into the reason why SQL would have an issue with being installed into the root of a drive. Is this bad practise? Why shouldn't I install SQL-Server to the root of my drive?

Why is it bad practice to install SQL Server to the root of a drive

When I install SQL Server into the root of my drive, for example D:\, I get an error when I run a database deployer from a third party piece of software.

But when I move my SQL Server instance to D:\SQL\ (move it to a folder within the drive) then installation works perfectly.

My question doesn't regard the database deployer but more into the reason why SQL would have an issue with being installed into the root of a drive. Is this bad practice? Why shouldn't I install SQL Server to the root of my drive?

minor edit
Source Link
Shanky
Shanky
  • 19.1k
  • 4
  • 36
  • 58

When I install SQL-Server into the root of my drive, for example D://\ I get an error when I run a database deployer form a third party piece of software.

But when I move my SQL-Server install to D://SQL/\SQL\ (move it to a folder within the drive) then installation works perfectly.

My question doesn't regard the database deployer but more into the reason why SQL would have an issue with being installed into the root of a drive. Is this bad practise? Why shouldn't I install SQL-Server to the root of my drive?

When I install SQL-Server into the root of my drive, for example D:// I get an error when I run a database deployer form a third party piece of software.

But when I move my SQL-Server install to D://SQL/ (move it to a folder within the drive) then installation works perfectly.

My question doesn't regard the database deployer but more into the reason why SQL would have an issue with being installed into the root of a drive. Is this bad practise? Why shouldn't I install SQL-Server to the root of my drive?

When I install SQL-Server into the root of my drive, for example D:\ I get an error when I run a database deployer form a third party piece of software.

But when I move my SQL-Server install to D:\SQL\ (move it to a folder within the drive) then installation works perfectly.

My question doesn't regard the database deployer but more into the reason why SQL would have an issue with being installed into the root of a drive. Is this bad practise? Why shouldn't I install SQL-Server to the root of my drive?

added 30 characters in body; edited title
Source Link
ypercubeᵀᴹ
ypercubeᵀᴹ
  • 98.7k
  • 13
  • 215
  • 305

Why is it bad practise to install SQL-Server to root of a drive

When I install SQL-Server into the root of my drive, for example D://D:// I get an error when I run a database deployer form a third party piece of software.

But when I move my SQL-Server install to D://SQL/ D://SQL/ (move it to a folder within the drive) then installinstallation works perfectly.

My question doesn't regard the database deployer but more into the reason why SQL would have an issue with being installed into the root of a drive. Is this bad practise? Why shouldn't I install SQL-Server to the root of my drive?

Why is it bad practise to install SQL to root of a drive

When I install SQL into the root of my drive, for example D:// I get an error when I run a database deployer form a third party piece of software.

But when I move my SQL install to D://SQL/ (move it to a folder within the drive) then install works perfectly.

My question doesn't regard the database deployer but more into the reason why SQL would have an issue with being installed into the root of a drive. Is this bad practise? Why shouldn't I install SQL to the root of my drive?

Why is it bad practise to install SQL-Server to root of a drive

When I install SQL-Server into the root of my drive, for example D:// I get an error when I run a database deployer form a third party piece of software.

But when I move my SQL-Server install to D://SQL/ (move it to a folder within the drive) then installation works perfectly.

My question doesn't regard the database deployer but more into the reason why SQL would have an issue with being installed into the root of a drive. Is this bad practise? Why shouldn't I install SQL-Server to the root of my drive?

Source Link
Sean
Sean
  • 233
  • 2
  • 5