Just make the column a computed column as PK + 199? I suspect that your requirement is a little more complicated than that, but it's difficult if you keep...

ronan.healy (5/22/2014)

---

thanks for that. will try that.

just 1 thing would that still work if say i had 10 different pieces of data in the second table that i wanted to...

You can set up a subscription that will e-mail the report as an Excel spreadsheet.

John

The only problem I've ever seen with that is if your job has a schedule. Your script will have a section something like this:

EXEC @ReturnCode = msdb.dbo.sp_add_jobschedule @job_id=@jobId, @name=N'Daily...

Something like this should work - a simple stored procedure with an @ErrorCount parameter. If @ErrorCount is 0, do nothing, otherwise raise an error that will cause the task...

You may be having intermittent network problems. Try setting up a continuous ping test and compare times of any dropped packets to the times you get the timeout errors.

John

Mark

I think your first problem is mathematical rather than programmatical. 400 values means 2^400 combinations, which is a much larger number than SQL Server can (as far as I...

Mark

Here's a couple of ways to limit the amount of processing you need to do:

(1) Work out the maximum rows you need to consider.

If you put all the rows in...

Try building the string you're going to execute as a variable and then PRINTing that variable instead of executing it. That'll make it much easier to see what the...

Nancy

Shrinking is fine as a one-off, so long as that table won't grow to 87GB again. If you think it will, leave the database as it is and ask...

I'm arriving in Telford at 8pm on the Wednesday, but leaving immediately after Thursday's proceedings have finished. Happy to share a couple of ales on my arrival if you're...

Indeed. Hence the warning about performance.

John

It's checking to see whether @Num has any non-numeric characters in it. Look up the PATINDEX topic in Books Online for more information.

John

Something like this should work, although performance could suffer since any index on ProGroup will not be used:

WHERE COALESCE(pg.ProGroup,'No Group') = @userParam

John

Karen

If you have a backup file (.bak), you can restore the database. If you have the database files (.mdf and .ldf), you can attach the database. The procedure...