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
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?
-
-
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
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.
-
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* -
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. -
Good point, thanks stevo_

-
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.
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.