Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
philipstratford
Starting Member
8 Posts |
 Posted - 2012-10-23 : 09:45:49
|
| I've been a DBA for databases running under SQL Server 2008 and 2008 R2 for several years and am very comfortable with it and know what I'm doing. However, we're now in the process of building the replacement for our production DB server, and I have the opportunity to install SQL Server 2012 rather than sticking with 2008 R2. The application people have said there's no problem from their point of view.My questions, really, are: Are there any strong arguments against me installing 2012 instead of 2008? Am I going to find it unfamiliar and that I'm thus less competent managing it, or is it broadly the same? Are there any obvious 'gotchas' that might make me think twice about migrating my databases from 2008?Cost isn't a factor. Thanks in advance for your help. |
|
|
Transact Charlie
Master Smack Fu Yak Hacker
3451 Posts |
Posted - 2012-10-23 : 11:16:42
|
quote:
"Cost isn't a factor. Thanks in advance for your help."
Nice.We are using some 2012 instances for non critical components -- so far we've had no problems. T think I prefer the visual studio esque version of management studio.We don't go to critical systems for a while though.Transact CharlieMsg 3903.. The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION. http://nosqlsolution.blogspot.co.uk/ |
 |
|
|
|
|
|
Should I Just Go For 2012?