In practical terms, they do the same thing: either allow a login to connect to the SQL Server instance or not allow it. They just do it in different...

You should look at SQL Agent fixed database roles. SQLAgentReaderRole might suffice for the user you want to view job history. http://msdn.microsoft.com/en-us/library/ms188283(SQL.90).aspx

I don't think there's a way to...

This is commonly done by importing data from the remote source into a staging table (we have a staging database containing permanent tables) in the destination instance, then truncating or...

Sorry, you'll have to provide more information or ask a specific question before anyone can help.

I know you'd prefer to keep the stored procedures and tables in the same database, but it might...

Here's an example of including the results of a query in the body of an email:

exec msdb.dbo.sp_send_dbmail

@profile_name = 'SQL Server Agent',

...

usman.tanveer (6/8/2009)

"

Msg 4305, Level 16, State 1, Line 1

The log in this backup set begins at LSN 149014000003456800006, which is too recent to apply to the database. An earlier log...

I think you're asking if you can install two instances of SQL Server on one server. If so, then yes, you can install one default instance (MSSQLSERVER) and one...

In SQL 2000, the option is also on the Advanced tab of the job step.

Are you sure you got the error when restoring the differential backup? I've only ever seen that when restoring log backups and I've gotten them out of order. ...

I've never had problems executing a package simultaneously. I suppose it would depend on what the package does, though. If it needs exclusive access to something, a file...

Okay, good luck. I haven't had any luck getting around the security.

You have to redeploy it to the server.

See my reply here: http://www.sqlservercentral.com/Forums/Topic728068-146-1.aspx

Save the package with a user password and an owner password. Anyone with the user password can execute the package but can't open or edit it. See "DTS...