Someone posted this a while ago

SELECT  FG.groupid AS GroupID

, SUBSTRING(FG.groupname,1,30) AS FilegroupName

, SUBSTRING(O.name,1,30) AS ObjectName

, ix.indid, ix.name as indexname

, F.filename as FileNames

FROM sysobjects O

 INNER JOIN sysindexes IX

 ...

>>Binding SQL Server instances to distinct IP addresses<<

You Can't ... unless you use clustering

hth

Raymond,

I overlooked that! and I am not able to test it but this should "kill" my bug

SELECT    

cl.CustID as Customer,

cl.CallStatus as Status,

RIGHT(cl.CallID, 4) AS...

You Probaly need SP4

check this KB 

hth

Two Problems

if you add up the maximum filed length of those you specified on the query it will be > 8060 (the maximum row size)

  you have to limit that...

But..

If you are planning to use many BIT columns and the table can be large guess what you can't index it it is...

Divide and conquer

SELECT    

cl.CustID as Customer,

cl.CallStatus as Status,

RIGHT(cl.CallID, 4) AS HEAT,

cl.PVCS,

cl.Title,

cl.CallDesc AS Description,

cl.RecvdDate AS Date,

JournalEntered,

j2.EntryText AS Journal

FROM        

 CallLog cl

 left join

 (select callid,...

First:

Can you verify all those dates are in the range-> January 1, 1900, through June 6, 2079

Second:

make sure that the SET DATEFORMAT dmy is used (as recomended above)

Third:

what is the...

Just Try the following in the posted order

• - do you have enough free space (and Permissions) in the target drive?
• - Antivirus Software not scanning/target...

I have to differ with that statement. When you have such large DB a product like litespeed will compress your backups on the fly therefore the copy and handling of...

Unfortunately that procedure has this limitations:

• Cannot handle more than 4000 chars in the sp body
• if the sp is splitted i more than one row on syscomments it won't work
• has to be...

Ok this has the limitation that only work for upto 50 years of service

I think it does what you want

sp_MSdependencies does uses sysdepends, therefore garbage in ...

yes that's the purpose for the delay but you have an explicit transaction opened that you should commit ASAP.

1 lakh = 100,000