It is true, that using Profiler may extend the duration of the test, as it will take up some resources, but in this case, I think that is acceptable. ...

If you can, do a profiler trace of the load test on sql 2008 and compare to a profiler trace on SQL 2012. You will likely find on SQL...

I am going to guess that the logging logic is toward the end of the stored procedure. When a client times out (command timeout expired), the client gives up,...

It may be possible, but it may be not under support. I currently have a SQL 2000 publisher with a SQL 2008 distributor/subscriber. You will likely want to...

After the upgrade to SQL 2012, did you change the compaitbility level of the database, update the index statistics?

Well, that was a quick test, anyway:

declare @boston datetimeoffset = '2014-05-20 12:00 -05:00'

declare @chicago datetimeoffset = '2014-05-20 12:00 -06:00'

select datediff (hh, @boston, @chicago)

Any chance you can use the datetimeoffset datatype? This will save the timezone information along with the local time. Datetimeoffset is a new(ish) feature in SQL 2012. ...

It's usually nice to have a backup admin (or two). So long as it does not affect the working of the application, you should be able to remove the...

Wow. Now that is a stack dump.

Anyway, since you have other clients (your laptop) that can connect to the SQL Server, we can rule out just about everything on...

You will need to create the logins for the database yourself. I think I saw an article about that on the front page here, today.

Once the database has been...

Nope. The page headers have already been updated. The compatibility level only affects what features are available in the database.

No. By default, the user will have no permissions (ALTER) on the dbo schema. Give it a whirl.

One thing to note, is that the ability to alter a schema carries the ability to drop existing objects in that schema.

You can think of a schema as a logical container of objects. When you grant permissions on a schema, you are granting those permissions on all of the objects...

I have never seen SQL Server take 30 minutes to compile a plan. My guess is that you do not have an issue with the plan cache being wiped...