I guess EM is still collecting informationschema-data. this may take a while. (we have setup a couple of dts-trials with db2 OS/390, there also it takes a while befor it...

maybe http://www.sqldts.com contains a solution for you ?

check out sqldmo ?

adding to phillcart 's reply :

and implement as backupsolution Full (weekly?) / diff ? (perf.impact) / and log (hourly) backups. according to a sla.

I'm having the same problem, but I'm using a workaround.

Open the VPN, use mstsc (remote desktop connection) to logon to a (sql)server and then open sqlEM and work from there...

start SQL Server in minimal mode from the command line (-f)

use Query Analyser :

use master

go

exec sp_helpsort

go

didn't run it over here 

euhm ... just slipped into my attention ...

... keep in mind your model-mdf/ldf have to be with the same charset as the old one or you can have some nasty things coming...

-- how to determin SQLServer Uptime

--  Tracking Uptime by Brian Moran http://www.winnetmag.com/SQLServer/Article/ArticleID/38042/SQLServer_38042.html

--

SELECT @@servername as ServerName, datediff(mi, login_time, getdate()) as SQLServer_UpTime_Minutes

FROM master..sysprocesses WHERE spid = 1

go

-- my own...

did you take a look at DTS to export to file ?

- take a look at SQLDMO

- maybe this can help you out ...

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=23&messageid=107508

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q220/1/63.asp&NoWebContent=1

"C:\Program Files\Microsoft SQL Server\MSSQL\Upgrade\scptxfr.exe" /s yourserver /d yourdb /I /F filepath

If you 're still using the default modeldb, you can copy another model mdf and ldf file from an other server ( dev ? )  to the datafilelocations of your...

did your temdb-file(s) autogrow ?

If this autogrow takes more time and the query times-out, you also get the message db-full , but the grow...

did you stop and restart sqlagent after you implemented the first alert ?

You have to when you implement your first active alert.

This generates the script you need.

SET nocount on

create table #tmpPKeys(

TABLE_QUALIFIER sysname,

TABLE_OWNER sysname not null,

TABLE_NAME sysname not null,

COLUMN_NAME sysname not null,

KEY_SEQ smallint not null,

PK_NAME sysname  null )

-- Get PK-info

insert into...

Is this what you want ?

It generates all needed statements without executing them !

-- creatie test case

if object_id('T_ParentMC') is null

begin

 create table T_ParentMC (

 col1 int identity(1,1) not null ,

 col2 int not...

Best practise is to always specify a specific database in your connectionstring !

Rule No x : never rely on a @#|$! default ! 

If...