Facing Slowness issue after migrating from sql server 2008(old server) to sql server 2016(new server

%3CLINGO-SUB%20id%3D%22lingo-sub-1762711%22%20slang%3D%22en-US%22%3EFacing%20Slowness%20issue%20after%20migrating%20from%20sql%20server%202008(old%20server)%20to%20sql%20server%202016(new%20server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1762711%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20a%20RDP%20server%20which%20is%20running%20in%202008%20version%20of%20SSMS%20and%20OS.%20Recently%20we%20migrated%20this%20server%20to%202016%20version%2C%20both%20the%20OS(2016)%20and%20SSMS(2016).%26nbsp%3B%3C%2FP%3E%3CP%3EConfigured%20new%20machine(with%20ssms2016)%20is%20same%20to%20the%20old%20one(with%20ssms2008)%20in%20terms%20of%20system%20configuration.%20It%20has%20a%2064-bit%20OS%20with%20x64-based%20processor.%20RAM%20memory%20is%2064.0%20GB%20and%202.39%20GHz%20(32%20processor).%3C%2FP%3E%3CP%3EWe%20are%20facing%20severe%20performance%20issue%20while%20running%20stored%20procedures%20in%20SSMS%202016%20version%2C%20as%20same%20code%20base%20has%20been%20migrated%20from%20sql%20server%202008.We%20are%20loading%20data%20to%20these%20servers%20using%20SSIS%20ETL%20tools.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20example%20if%20we%20are%20running%20a%20stored%20procedure%20in%20old%20server(with%20ssms2008)%20it%20is%20taking%201%20hour%20of%20time%20but%20the%20same%20SP%20is%20taking%2010%20hours%20of%20time%20in%20new%20server(with%20ssms%202016)%20sometimes%20even%20more.%3C%2FP%3E%3CP%3ETo%20identify%20the%20root%20cause%20we%20have%20tried%20below%20approaches%20but%20so%20far%20nothing%20worked.%3C%2FP%3E%3CUL%3E%3CLI%3EAfter%20migration%20we%20changed%20the%20compatibility%20level%20of%20sql%20server%20from%202008%20to%202016.%3C%2FLI%3E%3CLI%3ERestored%20the%20database%20once%20again%20from%20old%20server%20(ssms%202008)%20to%20new%20server%20(ssms%202016%20)%20without%20changing%20the%20compatibility%20level.%3C%2FLI%3E%3CLI%3ERecompiled%20the%20stored%20procedures%20in%20new%20server(ssms2016).%3C%2FLI%3E%3CLI%3Eupdated%20the%20statistics%20in%20new%20server(ssms2016).%3C%2FLI%3E%3CLI%3EDisc%20reconfiguration%2Fthickening%20of%20windows%20new%20server%20drives%20also.%3C%2FLI%3E%3CLI%3EWhile%20running%20time%20consuming%20stored%20procedure%20in%20new%20server(ssms2016)%2C%20parallely%20ran%20sql%20server%20profiler%20but%20nothing%20fruitful%20we%20have%20got.%3C%2FLI%3E%3CLI%3ERan%20parallelly%20same%20query%20in%20ssms%202008%20and%20ssms%202016%20servers%20at%20the%20same%20time%2C%20in%20old%20server(ssms2008)%20execution%20got%20completed%20much%20faster%20than%20new%20server(ssms2016)%3C%2FLI%3E%3C%2FUL%3E%3CP%3ENote%3A%20is%20there%20any%20solution%20we%20can%20try%20to%20get%20the%20same%20execution%20time%20in%20both%20servers.%3C%2FP%3E%3CP%3EThanks%20in%20Advance.%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3EPrashant%20Agrawal%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1762711%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAnalysis%20Services%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EBusiness%20Intelligence%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EData%20Warehouse%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIntegration%20Services%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1768913%22%20slang%3D%22en-US%22%3ERe%3A%20Facing%20Slowness%20issue%20after%20migrating%20from%20sql%20server%202008(old%20server)%20to%20sql%20server%202016(new%20se%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1768913%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F825874%22%20target%3D%22_blank%22%3E%40prashantagrawalbangalo325%3C%2FA%3E%26nbsp%3BI%20have%20been%20facing%20the%20same%20issue%20before%20and%20solved%20by%20enabling%20query%20optimizer%20fix%20at%20the%20database%20level.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hope%20that%20helps%20you.%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

We have a RDP server which is running in 2008 version of SSMS and OS. Recently we migrated this server to 2016 version, both the OS(2016) and SSMS(2016). 

Configured new machine(with ssms2016) is same to the old one(with ssms2008) in terms of system configuration. It has a 64-bit OS with x64-based processor. RAM memory is 64.0 GB and 2.39 GHz (32 processor).

We are facing severe performance issue while running stored procedures in SSMS 2016 version, as same code base has been migrated from sql server 2008.We are loading data to these servers using SSIS ETL tools.

 

For example if we are running a stored procedure in old server(with ssms2008) it is taking 1 hour of time but the same SP is taking 10 hours of time in new server(with ssms 2016) sometimes even more.

To identify the root cause we have tried below approaches but so far nothing worked.

  • After migration we changed the compatibility level of sql server from 2008 to 2016.
  • Restored the database once again from old server (ssms 2008) to new server (ssms 2016 ) without changing the compatibility level.
  • Recompiled the stored procedures in new server(ssms2016).
  • updated the statistics in new server(ssms2016).
  • Disc reconfiguration/thickening of windows new server drives also.
  • While running time consuming stored procedure in new server(ssms2016), parallely ran sql server profiler but nothing fruitful we have got.
  • Ran parallelly same query in ssms 2008 and ssms 2016 servers at the same time, in old server(ssms2008) execution got completed much faster than new server(ssms2016)

Note: is there any solution we can try to get the same execution time in both servers.

Thanks in Advance.

Regards,

Prashant Agrawal

1 Reply

@prashantagrawalbangalo325 I have been facing the same issue before and solved by enabling query optimizer fix at the database level.

 

How to steps:-

Right-click on database level then select properties then options then scroll down under database scoped configurations then select "Query Optimizer Fixes" change it to be "ON"

 

Or by running below:-

USE [DatabaseName]
GO
ALTER DATABASE SCOPED CONFIGURATION SET QUERY_OPTIMIZER_HOTFIXES = On;
GO

 

I hope that helps you.

Thanks,