We have a fresh install of SQL 2014 running on Windows 2012 R2 running in Production. We tested this extensively first and most of our code ran as fast as SQL 2012 or slightly better. Pure engine processes such as Backup jobs run about 30% faster. However, now that we’re in Production for the first day we’re seeing some very sporadic performance. For example, 90% of our jobs are running just fine. 10% of the jobs are running significantly longer. Jobs that used to take 7-8 minutes are now running in 40 minutes plus. Not only is this slowing down our server in general but it’s causing a lot of blocking issues.
We’re convinced this is a SQL 2014 issue and not hardware. Using iometer we can tell that this server outperforms our old server. SQL doesn’t always substantiate the numbers we’re seeing from iometer as far as performance compared to our old server.
We’re running on RTM, not Cumulative Update 1.
Our hardware is a beast of a server; DL580 G8, 384 GB ram, only 2 physical hard drives (running the OS/SQL) and the rest are Fusion iO cards. We have 9 total Fusion cards for the database, log and tempdb. Our old server is also a very robust server: DL380 G8, 384 GB ram, 48 physical drives and 2 Fusion iO cards for tempdb.
Has anyone else deployed SQL 2014? Has anyone else encountered these sporadic performance issues? If so, did cumulative update 1 fix the issues?
Separate question: If I put my database in 2012 compatibility mode and do a backup, can SQL 2012 read the SQL 2014 backup?
Thanks in advance,
André
André