I notice you mention instance, are you running multiple instances on this server, if so each instance must have it's memory set and not use dynamic memory.

How are you monitoring the sql memory, the situation you describe sounds unusual to say the least.

BOL and msdn site will explain locks and such like. use dbcc inputbuffer(spid) to see what was run to cause the lock in the first place. If you sort that...

I had a problem with this on a couple of Compaq servers ( at a previous employment), the problem was casued by a config change the ops guys made to...

Heaps still fragment at the leaf level if data changes, however, technically a Heap is generally best for bulk data import, once you need to update or delete the data...

What you most likely have is 2gb ram sat on the server resting its electrons 

Check the memory usage for the box in task manager, it probably...

You can't remove leaf level fragmentation from a table without a clustered index.

Only a covered index will bypass the actual table for data recovery.

A nonclustered index will require more i/o...

Depending on the structure and usage of your table, a table without a clustered index is a heap, which is fine if rows are added sequentially and no deferred updates...

Can't find the url I wanted, sorry, but this may lead you someway forward

http://support.microsoft.com/default.aspx?scid=kb;en-us;224453

I see the competition as maybe diluting the value of the site whereby answers given to posts are placed with no real attempt to answer the question. ( as can...

The database lock isn't a lock as such,  each connection generates a db lock as part of its process.

It's best to leave index hints out - using dirty reads is...

Server(s) have 4Gb ram, config checked by microsoft system engineer - I'm interested if anyone has had problems after increasing the available ram to a SQL Server using an oltp...

I usually avoid maint plans as they can prove prone to sudden failure - have you tried scheduling a std tsql backup job ?

Used SAN's for multiple servers etc.  A SAN should be viewed as for any storage for SQL Server and as pointed out should follow the normal rules. Certainly the logs...

I have to say that I have watched with some dismay the tendency of programmers/developers to automatically make the first column of their tables an indentity column without any real...