well you should be able to drop the database - however I'd have been through the logs first before rebooting, unless the database isn't important.  Stop the server and delete...

Sorry Andy - liked the article.

I generally dislike nullable columns, lots of nulls usually mean a poor design, however, sometimes you don't always have all the data - and lets not forget about apps that...

in real terms adding awe memory only increases the data cache which normally benefits reads the most, I'm not totally convinced it would help you adding an extra 512 mb...

when it gets that complex it might be easier to drop the database .. however you can usually place the truncate / drop code in a loop which doesn't exit...

It's a simple script, never had any problems, but that's probably down to documentation and I usually try to avoid large procs as they rarely optimise correctly in cache. If I...

not difficult - I usually drop this proc into master - can use it in from any database, will search for one or two strings

Create procedure dbo.sp_FindText

@wot varchar(250)=' ',

@wot2 varchar(250)='...

TYMA .. I'd normally assume that a production database is set to full recovery with regular transaction log backups .. if you switch the database to simple recovery you break...

selects don't work that way in a transaction and an updatelock isn't a select , selects can't give this behaviour.

You might have done better getting a dual core 64bit amd and moving up to 64bit. Workstation and server o/s have obvious differences but as a sole user it probably...

If you add a clustered index it will require a data sort, a secondary index will not impact the base table.  If you take the create another table approach make...

essentially no, a deadlock has to involve a data change. 

selects issue shared locks.

You can profile or check the procedure cache to see if auto update stats are running when you don't want them running. The reality is that the auto-update stats does...

I wouldn't advise doing anything with memory unless you add more physical memory to the box, any changes would most likely not have a noticible effect and as Steve says...

sounds to me that you need a DBA !  If you don't need to keep transaction log backups then put the database into simple recovery. You were close with your...