you can run the server side trace to capture what queries is taking longer than 500ms to execute. Note the time of the transactions and match it to the Perfmon...

how many transactions does the database see in a minute? The scheduled index rebuild may be causing the problem. I ran into a problem in the past with...

I had to run msdb.dbo.sp_sqlagent_notify to fix the jobs owned by sa.

This is an example of what I saw someone did. And there is only 1 file associated with the FG_TEST filegroup. I wonder if there is any benefit to...

for the test table, I would drop the table and recreate everything from a script.

try this

this is what I use to copy the backup file. in the job step 2, i restore the database.

declare @pathname nvarchar(100)

declare @fname nvarchar(50)

declare @bakfile nvarchar(200)

declare @cmd nvarchar(1000)

declare @destpath...

you have to create the server logins. Microsoft website has a procedure that allows you to script out the sql server logins with the passwords.

i think this is the one....

Try this.

Declare @SQL nvarchar(MAX)

Declare @docpath nvarchar(MAX)

Set @docpath = N'E:\Workflow\SPP\Attachments\ModelCodes\claim.xls'

Set @SQL = 'INSERT INTO [Tactical.Claim_LineItems_BULK_Audi] ([JObCreator], [ModelCode],

[ChassisNo], [CommissionNo], [AGSupport],[AVMESupport], [Brand], [Remark])

SELECT *

FROM OPENROWSET (''Microsoft.ACE.OLEDB.12.0'', ''Excel 12.0;;Database=' +@docpath+ ';HDR=YES'',

''select * from [Sheet1$]'')'

PRINT...

You can have the receipe/instructions broken down by line number and store them as separate row.

Leave the formatting to the presentation layer.

Why are you changing the partition function from monthly to weekly? Did the queries criteria changed?

In order to switch partitions, the source and dest must be in the same filegroup....

I used this in a job step prior to the lightspeed restore and it works fine restoring from prod to dev.

DECLARE @DatabaseName nvarchar(50)

DECLARE @SPId int

DECLARE @userid varchar(100)

declare @command...

Why don't you use SSIS to move the data? I can move 160 M rows using the Attunity drivers between 1 to 3 hours.

Use the CHARINDEX function

eg from the BOL.

DECLARE @document varchar(64)

SELECT @document = 'Reflectors are vital safety' +

...

use DTExec. You can pass variables into the packages.