Hi Perry,

Thanks for following me on this! Ok, I didn't drop the user yet...because like you said, it's working! lol

Also, yes this was a restored 2000 database and then upgraded...

Oh yes, definately did. The user is in the database and on the server. However, in the database the user shows Disabled, which it is not but in sysusers isenabled...

I'm sorry I'm not sure what you mean Perry? I run that procedure every time I move a database to a new server so am familiar with the syntax, here's...

Hi Perry,

Sure, the sp_change_users_login 'report' did not return any results.

Thanks!

Sandy

sorry, I cut off the last query, here's the results:

namesid

networks010xC2E15FFC2A12E24580EF2521D8BF3D94

gbagis_user0xC70796241EF53D4980E4A24429B629F2

GBA_USER0x66B0FF5767E31B469499BB7BE97B0B68

RemoteAlerts0x1DFC31A017ACC84FA870987E91F56F24

networks0x94E92A14CAEC434D9088C93EBD8206D5

namesid

dbo0x01

guest0x00

INFORMATION_SCHEMANULL

sysNULL

WFS_Editor0x426A4D5661452544854670B3A6B36889

sde0x93270AEBC0519044B7915ED41B44C417

gis_editor0xDF71297A7C4DEC46BAD1FF929E4CB04A

gis_viewer0xE9AE3EDB82B04C4BA6347D5B3ADBE2EC

gbagis_editor0x471D4616C15F6146A533DA54142CCE94

Since this is a critical user, and I cannot afford to drop it during working hours.. I will do this tonight:

- change the users schema owner from the user to...

Sure!

Here's the first output:

namesid

sde 0x93270AEBC0519044B7915ED41B44C417

gis_viewer0xE9AE3EDB82B04C4BA6347D5B3ADBE2EC

networks010xC2E15FFC2A12E24580EF2521D8BF3D94

GIS_Editor0xDF71297A7C4DEC46BAD1FF929E4CB04A

gbagis_user0xC70796241EF53D4980E4A24429B629F2

GBA_USER0x66B0FF5767E31B469499BB7BE97B0B68

RemoteAlerts0x1DFC31A017ACC84FA870987E91F56F24

networks 0x94E92A14CAEC434D9088C93EBD8206D5

WFS_Editor0x426A4D5661452544854670B3A6B36889

gbagis_editor0x471D4616C15F6146A533DA54142CCE94

Second...

Here's the output from the context under the database - I'm soo sorry, too much multi-tasking on my end:

namesid

networks010xC2E15FFC2A12E24580EF2521D8BF3D94

gbagis_user0xC70796241EF53D4980E4A24429B629F2

GBA_USER0x66B0FF5767E31B469499BB7BE97B0B68

RemoteAlerts0x1DFC31A017ACC84FA870987E91F56F24

networks0x94E92A14CAEC434D9088C93EBD8206D5

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

namesid

dbo0x01

guest0x00

INFORMATION_SCHEMANULL

sysNULL

WFS_Editor0x426A4D5661452544854670B3A6B36889

sde0x93270AEBC0519044B7915ED41B44C417

gis_editor0xDF71297A7C4DEC46BAD1FF929E4CB04A

gis_viewer0xE9AE3EDB82B04C4BA6347D5B3ADBE2EC

gbagis_editor0x471D4616C15F6146A533DA54142CCE94

Thanks Perry, I will! BTW - I appreciate your help with this AND my other question. It's great to know there's a community of SQL Profs out there when we're...

Thanks for your help! Ok,

I ran the report and it showed two other logins that were no longer registered on the server so I dropped them from the database after...

Hi Perry,

I'm not sure what you mean by this?

I actually thought I had fixed this.. by looking at it today in SSMS 2005 I see that the checkmark beside the...

Thanks Perry!

Can you tell me, if I do that on both my SAN and my physical box to compare throughput, do I have to use the same I/O for both,...

Reinstalled SQL and it is all good now.

Issue fixed.

Here's an article about the Snapshot Isolation Level. It looks like the preference is Read Committed in most environments however.

http://www.sql-server-performance.com/articles/per/new_isolation_levels_p2.aspx

It states that it will use tempdb more heavily so your...