If your data is numeric, store it in a numeric typed column. This will requier more work if your data-requierment changes, but it's a good practise to type your data...

Viewing the responses, you 'll notice that you'll have to test your solution !

My default is to put a clustered index on a table and to remove it if it...

When the package's job goes wrong, what's it saying in the jobs jobhistory ?

check the job-owner. Don't use a windows account as job-owner, it might fail with authentication-check.

take good care NOT having a windows-account as jobowner. (make it a SQLuser which has enough permissions to run the dts-packages)

If you are using a windows-account as jobowner, you'll find...

Yes, Yes, Yes

1. Should not be dependant on Outlook or MAPI components like Microsoft Exchange profile etc. Should be able to use POP3 or SMTP mail services to send mails.

2....

just to remind you sysdepends is not a full solution. (create a stored proc that calls an sp that does not yet exist. you'll get a notification)

- sql profiler for a while

- check its results

- sql profiler to support the next step and gather the errors

- rename 'tobedeleted' views to 'obsolete'

- after a while

- stop sqlprofiler

-...

The table is still functioning because the row-data-length did not yet reach the maximum limit for a page.

However, sqlserver did raise a warning regarding this issue at creation time of...

check http://www.riverland.net.au/text/look_first/netcode.html

it has a litle list and also has some smily explanation.

There also exists a sp_cycle_errorlog.

Downside of this is that it apears not to be working when used in a sqlagent job.

(complaints abount not being sa, even if I make sa...

correct, noeld.

if you have e.g. hp-openview monitoring software, you could have your last step raise an error (user defined errormessage / alert) to the windows eventlog, and hp-openview could pick it...

AFAIK there is no feedback to the job launched by sqlagent and it will only document that the job is started by the alert-related jobschedule. Based on this, I guess...

script it from the old db and run the script on the new db, removing the script-references to the old db.