you'll be able to see if connection pooling is taking place by looking in a profiler trace against that database for a lot of sp_resetconnection commands

are you using connection pooling ? that would most likely be the problem.

what jdbc drivers are you using ?

after you cut down the data did you update statistics ?

might be that the query optimiser isn't picking the best plan for you due to out of date stats

i'd also...

there is a dubious piece of information somewhere on microsoft's site stating that for "optimal" performance a database should have as many files as there are CPU in the machine...

I normally go for the approach of moving all of my indexes into a seperate filegroup first. (if this is on a different array defrags are faster)

then move text objects...

I think the biggest thing you can do to get this runing well is to make sure you put the best disk config in possible. SQL standard will only support...

this kind of naming can cause real problems - never include a decimal point or space in your database name

i'd advise changing to the following

select a.Emp_no,a.Emp_Name,a.Faulty_ItemSLNO,

b.Item_Name as Faulty_Item, a.Date_OfRep, a.Replacement_ItemSLNO,

c.Item_Name as Replacement_ItemName,a.Date_OfAlloc

from Item_Allocation a

left join Item_Master_Table b on a.Faulty_ItemSLNO=b.Item_SlNo

left join...

is sql2005 set to "allow remote logins" in the footprint configuration tool

can you post a create table statement for one of these medicservicefeed tables?

you can also use union hints

select x,y,z from a union all

select x,y,z from b

option(CONCAT UNION)

which will "attempt"...

select @@version

SELECT SUBSTRING(@@VERSION,21,CHARINDEX('(',@@VERSION,1)-21)

should give you just the version number major and minor part without text

as long as your full backup is INIT and your differentials are NOINIT you're on course for having the right backups

(assuming they both go to the same file)

then we would...

you could create 2 steps for each "logical step"

on success of step1 call step2a

on failure of step1 call setp2b

setp 2a just does sql code

step 2b does an xp_sendmail (or whatever...

NOINIT will be causing your backups to append - that's why the backup is growing - it should be 1.5GB accordig to your figures

ok - so we bit the bullet and applied it to the cluster at 6am this morning. It is cluster aware (apparently the patch was withdrawn in march because the...