Upgrade from SQL 2008 to SQL 2012: do we need to change connection string?

We are seeing some terrible performance degradation having just upgraded our MVC4 application from SQL 2008 to SQL 2012.

Queries run directly in management studio on the database server run somewhat slower than they did prior to the upgrade (up to twice as slow).

Queries run from the web server (a separate machine) run hugely slower, some more than four times slower. We pointed the finger at the network between the two machines, but our hosting company have suggested that the connection string should have changed for SQL 2012. I'm not aware that SQL 2012 connection strings are any different to SQL 2008 connection strings - am I right?

Thanks!

Our connection string has been unchanged for years and looks like this: Server=111.111.111.111;Database=MyDbName;User ID=MyDbUser;Password=MyDbPassword;

UPDATE: This eventually turned out to be a faulty physical port on the firewall!

Solution 1:

No. Connection strings have not changed for some time unless you use one of the new connection-based features and while there are some in between the versions you have (availability groups) they are not relevant when not used.

So, in your case - definitely nothing has changed.

You will have to run a profiler and find out why. This is something you should have done before upgrading production - standard approach.