i found the answer, I had to create a credential and a proxy. thank you though!

http://msdn2.microsoft.com/en-us/library/ms187901.aspx

😀

Try checking out the scripts here...

http://www.sqlservercentral.com/Forums/Topic459785-146-1.aspx

Scott's worked perfectly. Thank you so much!

😀

so far I have this but it only seems to bring back public role.

SELECT DISTINCT sysdatabases.name AS [Database], sysxlogins.name AS [User], sysusers.name AS role

FROM ...

It looks like the proc fixed itself transferring from 2000 to 2005. This is the script output.

You can try this script and change the order by if needed

select convert(varchar(30),

object_name(id)) [Table Name],

rows

from sysindexes

where object_name(id) not like 'sys%' and indid = 1

order by...

Awesome!I'll try it out... thank you!

You have to have permissions to create objects in master or try logging in as sa...

Found something that works!

Thanks all!

1) Expand Schemas(should be like a folder under Security) .

2) Delete the unwanted "userSchema".

3) Then, go back to the User(a folder like thing) and...

Here is the exact error I get when I try to delete.

TITLE: Microsoft SQL Server Management Studio

------------------------------

Drop failed for User 'asava'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Drop+User&LinkId=20476

------------------------------

ADDITIONAL INFORMATION:

An exception occurred while...

I get nothing returned when I run that... strange. I receive a list of orphaned users, try to delete, can't because it owns schema, but when I run the select...

This article when the script is run shows 'sys' as an orphaned user. Be careful...

It might be something as simple as clicking on the actual file group name in the select list.

Even though it says it is used for sql 2000, I used the sp_helprevlogin and sp_hexadecimal to go from 2000 to 2005.

http://support.microsoft.com/default.aspx/kb/246133/

I'm not sure what else it could be, you might want to double check all the above mentioned... making sure both servers are on the same security, both servers have...