Eric M Russell (11/13/2013)
Dale Turley (11/13/2013)
I strongly disagree with the idea of just pushing something out to fit a time frame, and this kind of mentality is the reason for IT having such a bad name. It also gives rise to the phrase, 'Don't use the software until the first service release.'If I brought a television that worked most of the time but couldn't show certain channels for example or had faults, I would return it for a refund, and if it was not put down to a faulty unit I would use another company / brand next time. The same with software - it's the reason why lots of software does not get used within our company and to be frank, won't get a trial again for the foreseeable future.
I recently tried using SSMS 2012 and it is so riddled with bugs that it is uninstalled and I am back to using the 2008 tools. With SSMS being so riddled with bugs, I have no intention of trying the database engine any time soon. 2008 works perfectly for us.
Curious, what bugs did you encounter in SSMS 2012? I installed it a couple of years back, use it most every day for both development and admin, and don't have any major complaints.
My SSMS 2012 has to close from errors a couple of times a week. If I have to compose a nontrivial amount of T-SQL I try not to do it in SSMS and if I do, I make sure I save copies elsewhere.