Using Windows authentication you can't. The only way you could differentiate permissions is by resorting to an application role. However, that has its own issues.

However, also check the upgrade scripts left by the service packs, also in the same directory. If they update a stored procedure during a service pack, it's not going to...

It runs under the context of the user who performed the operation (whatever user is making the database connection in the example of your ASP page). However, ownership chaining rules...

#1 Yes, GETDATE() returns time based on the server. The server is unaware of any timezone information of the client.

#2 No, not within out passing in something via a...

The msdb database holds the DTS packages and the information on the SQL Server agent jobs.

A search on support.microsoft.com turns up quite a few hits for 8264 internal sql server error as the search query. Several look like they might apply...

Tech event: SQL Server 2005

MNF Memory: Brett Favre throwing for four touchdowns as his receivers caught just about everything he tossed up shortly after his dad died. Second would...

I currently have it on one server in production, but it does non-critical reporting. Haven't seen any issues with it there.

You can't remove guest from master and tempdb. You can from msdb, usually with no ill effects. The information in msdb isn't something most users need access to. You can...

If you're using AWE, you'll need to install the hotfix as SP4 has a bug with respect to AWE memory. I think that's the main bug people have noticed.

Try temporarily having SQL Server listen on a different port and see if you can make a connection to server,port. I seem to remember this issue happening and by switching...

No, they work through SQL Server. One of the issues with netstat, however, is that except in WindowsXP where you have the -b option, you don't know what is listening...

Is the DTS package referencing the batch file differently than the job which directly runs the .bat file? In other words, same exact path, etc.?

Yup. If you can't go to SP4 and use the switch, this is the way to go. If you're on SP4, the switch should be sufficient.

One small point... I don't believe SQL Server Agent is actually executing xp_cmdshell. That would require a connection to SQL Server and then having SQL Server execute the extended stored...