Since SSIS is server based instead of instance based, there didn't appear to be a good way to look at the instance. I will look into the information that...

Now that my memory has been jogged, we did use DTS (for runner to SSIS) with an ODBC driver to move data from Informix to Sql Server before we migrated...

We used to us dbschema to unload data from an Informix database on Solaris, ftp to move it to the Windows Server, and bcp to load it into Sql Server...

So you can't dedicate 1-2 days a week to learn or explore something else. How about spending 1-2 hours a day? Maybe even come in early to work...

Here's the script that I run to check for old processes. It works with both SS 2000 and SS 2008. Appreciate the reminder about new system tables. ...

I wasn't sure but I thought it was worth a shot just in case it might help. I think we have a tendancy that when we find a solution...

This may not apply to you but when I Import Packages into MSDB, I set Security to Server Storage and this can solve problems of running from a job.

Steve

Roy,

I found out that my problem was not starting the SQL Server Browser on the instance of Sql Server Express so it did not allow remote connections. I had...

I you really want to be quick and dirty, I believe you could add the public role as a member of the db_datareader role in each database. I've never...

Roy,

Thank You. I will check it out and let you know how it goes.

Steve

Haven't seen any response yet. Also, haven't seen it on the Newsletter.

Steve

I would make a database role, add users to the role and assign the permissions to the role.

You assign the permissions only once and you can add or delete users...

It IS unclear whether the Orig Poster thinks the sa user stands for Service Account or they really meant changing the password on the Account the run the Sql Server...

Be sure to have at least one other user with the SysAdmin Server Role so you don't lock yourself out.

Steve

If you are getting the error when try to set up a Clean Up job, I would look up the reference in BOL for sp_delete_backuphistory, sp_purge_jobhistory or sp_maintplan_delete_log and try...