I think the only possible solution would be dynamic SQL. Get all your info (including required fields, alternate fieldnames, tables, etc.) from the client and build the query with this...

I've read your first post again and noticed something. You are using DTSRUN in your command prompt. The dtsrun command prompt utility (dtsrun.exe) that was used in SQL 2000 has...

steps to generate the automated process:

- manually go througt the RESTORE GUI and generate a script for the complete restore command

- change the name of the backupfile in the generated...

If I understand correctly, you want the values out of a dynamic number of colums and use these values to create a new query.

It takes several steps to accomplish this....

Remember: if within a CASE statement the WHEN clause is TRUE, the following WHEN statements and the ELSE statement is not executed anymore.

So if some data in your example contains...

No, you should put the "EXEC sp_trace_setstatus 2, 1" command in the IF block, just before or after the mail command. Because of the "not exists" check, the first IF...

Check the recovery model of the database. If it is in FULL recovery you need to take frequently LOG-backups (every 15 - 30 minutes). If you don't do that the...

You have mixed Visual Basic language (private sub....) with T-SQL (Select Case ....). Those languages can't be combined in one statement.

The code you stated is more Visual Basic then T-SQL...

Open a command prompt on each node, navigate to the root of the disk and execute "dtexec /?" (without quotes). Compare the version number in both outputs. They should be...

I guess the outlining is not correct in your view due to a (very) different length of the data in each row. In most text editors tab-stops are pre-defined. When...

Thanks Jeff.

And especially on the internet this is...

Like Matthew before mentioned, the subsequent criteria is only checked when the previous is failed. You could combine the criteria with an OR statement

SELECT

[Response]

...

The mail generated by the Job Notification system is predefined and AFAIK it can't be changed. The only way to accomplish your request is to create your own messaging system...

place the mail procedure inside an IF statement

IF not exists(SELECT * FROM ::fn_trace_geteventinfo(2))

BEGIN

EXEC msdb.dbo.sp_send_dbmail @profile_name = 'DBA Alert',

@recipients...

No databases will go offline. It wil generate error level 17 messages stating "object xx can't be created in filegroup yy for database TempDB" and the transaction(s) will be cancelled...