SQL Server Express + Vista = No file

Posted By: javamdk | Jul 4th, 2007 @ 12:58 AM
page 1 of 1
Comments: 5 | Views: 1432
#Jul 4th, 2007 @ 12:58 AM
javamdk
javamdk
Innovating Tomorrow's Technology
Ok, where to start... I'm using SQL Server Express 2005 and trying to attach a database in a folder called "blog" on my Desktop.

I attached a picture of SQL Server Management Studio when I'm trying to locate my MDF file. Although, under the user Joseph is nothing Sad I'm running this app as admin, but I'm sure this has something to do with the security elevation. Other than that, what gives?

sql attach
#Jul 4th, 2007 @ 1:29 AM
blowdart
blowdart
Peek-a-boo
javamdk wrote:
Ok, where to start... I'm using SQL Server Express 2005 and trying to attach a database in a folder called "blog" on my Desktop.

I attached a picture of SQL Server Management Studio when I'm trying to locate my MDF file. Although, under the user Joseph is nothing Sad I'm running this app as admin, but I'm sure this has something to do with the security elevation. Other than that, what gives?



You're right, it's a permissions issue. And it has nothing to do with Vista either.

SQL Express runs as Local Service or Network service. Those accounts cannot see into "Documents and Settings", they just don't have permissions, thus the behaviour you're getting.

You either need to move the database out of your desktop and somewhere under c:\ or give permissions to the SQL Express account. Note that if you copy it out the permissions will remain with it sometimes and so you should reset them after.
#Jul 4th, 2007 @ 6:40 AM
javamdk
javamdk
Innovating Tomorrow's Technology
Well what's the true point of 'hiding' the current users directories. What's SQL Servers point of doing this, wouldn't storing it in root C:\ be worse (theoretically). I would think a database file with system files and directories would be worse than with pictures and common documents by the users folder.

*shrugs*
#Jul 4th, 2007 @ 6:45 AM
stevo_
stevo_
Human after all
Mmm, not really - an sql server in a published environment shouldn't really worry about users having access to it's drive. It should worry about people even getting to that level of access.

SQL runs as a service, because thats what it is, it doesn't make sense that a service should be reliant on a users space.
#Jul 4th, 2007 @ 6:49 AM
javamdk
javamdk
Innovating Tomorrow's Technology
Good point, thanks stevo_ Cool
#Jul 4th, 2007 @ 7:42 AM
blowdart
blowdart
Peek-a-boo
javamdk wrote:
Well what's the true point of 'hiding' the current users directories. What's SQL Servers point of doing this, wouldn't storing it in root C:\ be worse (theoretically). I would think a database file with system files and directories would be worse than with pictures and common documents by the users folder.

*shrugs*


It's not hiding at all. It simply doesn't have permissions to get in there, hence clicking on the folder brings nothing back. This is not purely a SQL problem, it's NTFS permissions, nothing more.
page 1 of 1
Comments: 5 | Views: 1432
Microsoft Communities