the problem is the logical design of the db - having 100 FK's is extremely suspect as far as good design goes !

when the query processor compiles the

...

when you attempt to create TABLES with SSMS you are given the designer grid to name columns, datatypes etc

instead of pressing the OK button, click the GenerateChangeScript on TableDesigner menu...

there are several FREE source-code control systems available (eg subversion)

http://subversion.tigris.org

and this specifically for SS2005 objects using VSS

http://www.codeplex.com/SqlSource

also view these concerning VSS

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=365068&SiteID=1

http://blogs.msdn.com/richardb/archive/tags/vss/default.aspx

logical reads [and writes, CPU, duration] will be aggregated during your user session

- when you logout you get these totals [they are not for the actual logout itself!]

in your example...

suggest that you first try these commands in a query

SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED

select A=count(*) from master..sysprocesses

select B=count(distinct hostname) from master..sysprocesses

select C=count(*),hostname from master..sysprocesses group by hostname order by...

there could be several causes of this bad behaviour

1. network glitches

2. SQL glitches

3. SQL config

4. hostile code

from your description the problem has got worse so it sounds like 1.

- any...

in SSMS GUI you can prepare to create a new db but press the "script" button/combo to generate the TSQL in a new query window (then click cancel so its...

the SQLCMD utility can discover all the SQLserver instances [that haven't chosen to be hidden]

so here are some horrible hacks for you ...

HACK 1 (bad!)

at the command prompt (ie start...

the server "listens" on one/many network protocols/ports, so clearly your client-side must pick [at least one of] those [via network/aliasses part of sql config tool]

some SQL installs (especially SQLEXPRESS) deliberately...

select *-- data files (*.MDF)

from sysfiles

where (status & 0x40) = 0

select *-- tranlog files (*.LDF)

from sysfiles

where (status & 0x40) <> 0

as per BOL

http://msdn2.microsoft.com/en-us/library/ms178009.aspx

but also notes you...

you should create the maintplan, and this creates the SQLAgent job(s)

if you start fooling with the job, the maintplan and job may differ and can get you into trouble

- so...

that SSC article was written in 2004 so pre-dated SS2005. you should now also consider database mirroring. each has de/merits.

my suggestion is Log-Shipping for D/R as you can recover to...

BOL shows you the syntax for SQL2005, SQL2008

http://msdn2.microsoft.com/en-us/library/ms174269.aspx

http://msdn2.microsoft.com/en-us/library/bb522682(SQL.100).aspx

so you should try command like

ALTER mydbcopy TRUSTWORTHY OFF

new db gets cloned from model so you should change model...

IMHO your requirement has very little to do with DW (ie SSAS) and a lot to do with OLTP (ie SQLSvr)

if you are dealing with help-desk etc you need immediate...

correct, that query must be posted to [worker in] each partition [whether local or federated]

you can+should have secondary indexes for each partition [hopefully the same on each!] which will help...