when you say you've run out of space - what do you mean ?? the drive is full?

he's helpfully commented out an example proc call at the end

-- #sp_shrinkdata @updateusage = 1, @freed_space = 100 , @Msg_rtn_intv = 10

just remove the --

can you post the results of the query

exec sp_helpdb varuna

doing a bit of research - MERGE has been included with SSIS but not as part of the T-SQL after Beta2

you can run the nice shiny merge command using SSIS...

you may be able to get it from the connection string in the apps - depends on your app

lesson learnt - never use SA account for your apps or reporting

I don't think there will be many DBAs telling you how to hack the 'sa' password on their boxes.

if you're the DBA and you've forgotten the sa then i'm sure...

unfortunatley microsoft removed it from 2005

i've seen talk that if you buy visual studio 2005 there is an sql developer/debugger in there - but that's a lot of money

rcovery model is down to what recovery options you need.

there are 2 basic modes in sql 2000/7

simple mode (or in sql 7 truncate log on checkpoint on)

in this mode you...

if only 100mb of the 1.3gb is used you don't need to truncate the log - you need to shrink it.....

trunctate log means to remove the inactive entries from within...

you might have to post your script, but i'm guessing that you have not filtered out stored procs or you have a "dodgy" join in your script.....

looks like we're not the only ones to come up agains this

http://www.geekswithblogs.net/sabotsshell/archive/2005/08/20/50706.aspx

hmm - i've just tried it as well and got the same problem - looks like it's been removed from 2005 since the beta.

documented in 3 of the books i...

should do - but you may find that logging out the user that's getting these errors from all devices should also fix it.

i'm sorry - but some of the recent questions have been a little "open to interpretation" !!!!!

what may work for one situation won't work for another - i can't possibly...

it's a log in failure or connection failure - usually occurs for us when someone changes their password but is still logged into sql server - when they try and...