Hmmm...so that did it. I thought I had been downloading 3.5 SP1...file name was the same, file size was the same. And I'm still not sure why it...

I said in my initial post we only have the binaries in C:, the stuff that goes to C:\Program Files. No data files in C.

Thanks for the replies. I think the root cause of the issue is that our C drive was 9 GB to begin with when we started with SQL 2000...

You can't shrink below the initial size. Your only option is to back up the database, drop and recreate it with a lower initial size, and then restore. ...

Any progress here? I'm having the same issues. At one point we had no issues, then it stopped working a couple weeks ago. When I kick off...

Nope, it's a database that's been up and running for a while now. Data was already in the table when the full text index was created on it.

Resolved my issue. I granted the user that owns the package SQLAgentUserRole role in the msdb database.

Yes, I understand the tradeoff for simplicity is enhanced security. But most people I know like(d) SQL Server because it was a quick and easy RDBMS to set up...

Wow, and a proxy requires credentials etc etc. Way too much additional overhead for what I want to do. Thaks for the replies.

And thank you Microsoft for turning...

I understand that, the user is not sysadmin so it should run under it's own security context.

Running SQL Server 2008, RTM.

Thanks, but that didn't help. ANd it defeats the purpose...I want to only be able to access my remote db2 system using that cbsdba user. If a login...