Will this affect their database at all?4. I assume that I'm looking at downtime on their custom application/database - Would this be correct?3. Can someone summarize what is contained in the master database2.
They have one custom application that uses a single SQL database and very little security customization (the custom application uses one Windows AD account to access the database).Basically, I'm wondering:1. I believe the rebuild should be fairly easy, but just don't have a full understanding of what it will affect.
I have tried restoring the master database from a version prior to the crash, but I still have the same issue. Otherwise, SQL seems to be running okay.I have come to the conclusion that I probably need to rebuild the master database. The only other issue that I've found is that a maintenance plan doesn't quite work correctly - It will backup their database, but not delete old copies off the hard drive. Anyway, if I go into SQL Management Studio and try to pull up properties of any database I get a "cannot show requested dialog" error. I have a client who is running SQL 2005 (as part of SBS Premium), who experienced a server crash due to the database "administrator" filling up the C: drive with manual SQL backups. I've been in support for over ten years, but have had minimal exposure to SQL. We've got lots of great SQL ServerĮxperts to answer whatever question you can come up with.
0 kommentar(er)
