In our development environment, we give dbo access to the databases that the developer is working with, but not server(instance)-wide access.

Additionally, you can create a job to store information about blocked/blocking processes.

Create a table to hold the results:

if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[blockingprocesses]') and OBJECTPROPERTY(id, N'IsUserTable')...

Steve,

Thanks for your reply - not what I was hoping to hear, but kind of what I was expecting to...

Thanks for your respnse.  The column mappings look correct, but it's difficult to see the values because the name of the data file is dynamically generated as needed.  I use...

If they're depoyed to msdb rather than filesystem, I don't think that they will show up under integrations services (I may be wrong).  You can query msdb, though:

select name

from sysdtspackages90

That...

In Enterprise Manager, if you go under the Management Section, SQL Server Agent, Alerts.

In the dialog box:

Type - "SQL Server performance condition alert"

Object - "dbname/Databases"

Counter - "Percent Log Used"

Alert if counter -...

From BOL:

Right-click a server, and go to Properties

Click the Connections tab

Under Remote server connections in the Query time-out (sec,0 = unlimited) box, choose an value between 0 and 2147483647 to...

You can do an update statement to the sysdbmaintplans table to set a new value to  max_history_rows.

UPDATE sysdbmaintplans

SET max_history_rows = n

where plan_name = 'your plan name'

The database being moved needs to be completely offline prior to moving the files. 

Try sp_removedbreplication 'dbname' where dbname is the name of the published database.  Removing replication is tough when it's broken - good luck.

You need to use the Transfer Logins Task rather than the Copy SQL Server Objects.  Passwords aren't scripted for security reasons.  You can refer to the article below:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q246133