Restoring with standby can place a LARGE overhead on the restore of each transaction log backup file.

Leaving the database in standby means that SQL Server has to leave the database...

I agree with Anthony... a calendar table is probably a better idea, but this should get you the first day of the previous quarter.

declare @d datetime

set @d = getdate() --...

Without seeing table definitions, nobody will be able to give you a definitive answer.

At a guess, should this line

LEFT JOIN PriceIndex A ON A.PriceIndexId = P.PriceIndexId

really be

LEFT...

Just put the 0 in quotes...

select [District],substring([District],0,charindex('.',[District],1)),

case when ascii(substring([District],1,1)) between 48 and 57 then [District] else '0' end Dist

from tmp_dist

I have seen this message (and various others) frequently when trying to replicate over slow/poor quality network connections and/or poorly performing servers. They have usually been followed (eventually) by a...

Beats the heck out of me!

I think you can (not that I'm advocating it)...

USE tempdb

GO

CREATE PROCEDURE obj_cursor @obj_cursor CURSOR VARYING OUTPUT

AS

SET...

The screenshots you've shown are for SQL Server itself. SQL Agent is a completely different service.

Look for a service called "SQL Server Agent (MSSQLSERVER)", and see if that is started.

It probably a good idea for you to have a look at the topic in books online first, then post back with any specific questions.

http://msdn.microsoft.com/en-us/library/ms151223(v=sql.90).aspx

You might want to have a look at the Agent Profiles.

You can create your own profile and add the error number to the -SkipErrors list in order to ignore...

Assuming your sample data is representative of the real data (i.e. level will always convert to numeric, you don't have lower levels e.g. 1.2.5), won't this do the trick?

select level...

"Not for replication" on a foreign key instructs SQL Server not to check the constraint when the update to the FK column has come from a replication source.

As a...

The Microsoft "System Information" app will show sector sizes for each disk under the storage section.

I'm not talking about anything overly scientific... even a simple copy of small and large files should be way quicker...

Are you sure it's SQL Server that's the problem?

Have you run some simple benchmarks on the new server vs the PC?