n00bDBA (10/9/2012)
So apart from creating non-clusterd unique indexes on all there primary keys.. which from what i gather is pretty wierd...
No, clustering all your PKs is actually what's usually weird if you like performance... 🙂
My questions are.. If you have a role that has insert, update, delete select and references (Not sure youd need that one) on all tables and execute on all stored procedures
Why would they then say that all users need to be db_owner. Surely this is counter productive as db_owner can do all of those things and drop any table view sp they like..
Were things different in SQL 2000?
Not overly. Do they allow schema customization from the front end? It sounds like they setup some kind of tables to be customizable from the interface.
Is there another/better way to see what the schemas do? Or again is there something related to SQL 2000?
Not really. 2k schemas were more organizational (other than table redirection) than anything else. They also created by default and it sounds like they should have simply been removed. Most of the security and stuff didn't really come into play/get used until 2k5.
It sounds like it's an antique built by medium level folks and you're just stuck with an unupdated version as they learned more. *shrugs* Not utterly uncommon.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA