Some more additional information:

You can drop them from node (where SQL server reside) local NT group. A couple minutes ago I tested that. Than I successfully changed dbowner from non existing local...

If they doesn't work for your company so why their logins are still in your SQL server?? You should change the dbowner and other objects, where they are dbo,  owner...

In theory yes you can change it to sa. But on my oppinion it would be better to change to a existing domain login, who have sa rights. Sa as db...

Why cann't you simply create a backup of your DB ? Then after restoring it you will have the DB structure and the data. Friendly speaking I donn't understand why...

Once I had something like that. I couldn't do this through a QA but successfully did it through an EM. But first I backed up my DB and then shrinked...

Thanks Nicholas. You have mentioned about physical or hardware problems here. What's about the software problems? Have you ever experenced or maybe heard about it? I mean maybe there are...

In theory you could upgrade.

Don't forget to make logins script and backups of your DBs in case of a some misunderstanding

On my oppinion  it is needed to keep the query from returning metadata only. I had this problem a  little bit  earlier than you so somewhere I found out this....

In this case try the following proc first:

exec sp_serveroption 'ServerName', 'data access', 'true'

Did it help?

Hi,

try the following script

select * into #tmp1

from openquery(ZZZSERVER,'set fmtonly off;exec master.dbo.sp_helpdb')

select * from #tmp1

Good Luck!

Detailed explanation of your problem:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/createdb/cm_8_des_03_89pv.asp

Why is the separate folder being  the main problem for you? Why cann't you simply write particular .mdf and .ldf files location in a script as it was suggested previously? Maybe I...

... or you can do this through Enterprise Manager. Point to Databases then All Tasks and then Attach Database...

If you have a lot of DBs and need to attach them...

You can try to write your  objects cursor and then execute sp_changeobjectowner

Strange. In normal circumstances it should work.

If you created DB with the CREATE DATABASE statement,  Change/add the following registry keys:

HKLM\Software\Microsoft\MSSQLServer\MSSQLServer

VALUE: DefaultData

VALUE: DefaultLog

It should help, but be carefull, because of wrong change...