Had our database shutdown in the middle of the night last night; our variable length BI extent filled up. Not sure if it was the right thing to do, but I just added another bi extent.
I believe the problem was caused by a piece of code that we run quarterly; it is a big process, and this is the first time we've run it after updating to the newest rev of our system. So I am going to research that and make sure the problem doesn't occur again, but I really hate having that 2GB bi extent just sitting out there. It probably doesn't matter, since BI is on it's own disk pair and I never come anywhere close to filling it...but I'm a neat freak I guess.
I'm thinking just truncate bi, do an offline backup, delete and rebuild the database (with my desired BI structure) and restore the database. Am I on the right track? And is there something different I should have done to recover?
I believe the problem was caused by a piece of code that we run quarterly; it is a big process, and this is the first time we've run it after updating to the newest rev of our system. So I am going to research that and make sure the problem doesn't occur again, but I really hate having that 2GB bi extent just sitting out there. It probably doesn't matter, since BI is on it's own disk pair and I never come anywhere close to filling it...but I'm a neat freak I guess.
I'm thinking just truncate bi, do an offline backup, delete and rebuild the database (with my desired BI structure) and restore the database. Am I on the right track? And is there something different I should have done to recover?