Before any fixes that you think are "essential", make sure your manager agrees the priorities, in particular new work vs schema fixes, backups, reindexing or DBCCs etc
Only do essential fixes initially - if the system has been working for a few years then it can probably work for a few more weeks (even without PKs)!
If you make changes, and something breaks, then some users might think you don't know what you are doing. You also might get blamed for (schema) problems that come to light subsequently.
Before you get into making schema and other changes (but I see that you have already started), make sure you have a way of tracking the changes, eg use some sort of schema source control system.
Hope that helps
I strongly agree with what Steve wrote above. If you operate alone and without a net, you will die when you fall because you will fall even if you're a great DBA that never makes mistrakes. :-P
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs