general rule: more updates (in a timeframe), means creating/rebuilding with a lower fillfactor. Thus, for read-only data, set filfactor to 100. (fillfactor is the amount of free space in a...

Aha! :w00t: thx for the update

Funny,

According to Slave Oks (http://blogs.msdn.com/slavao/archive/2005/04/29/413425.aspx, very interesting article), he recommends enabling AWE.

Also, check BOL for the item Serverproperty

AWE is used for locking memory in a 64bit environment. So if you have al lot of memory, anable AWE and 'lock pages in memory'

If you don't lock your memory,...

Seems you're running one (or more) snapshots and you're running out of diskspace (unable to store the original data in the snapshot).

If you're not able to reclaim diskspace, delete...

You could change the collation with the command

alter database collate ... (see BOL)

However, I don't know what the impact is of this command. AFAIK, It requires an exclusive...

you have 2 choices:

1) either change the recovery model to simple and do a shrink on the logfile (if it's very big). drawback: you can't do a PIT recovery, so...

The problem is that shrinking (on a logfile) only truncates the free space at the end of your logfile (an almost exact question was also on this forum this week,...

In order to check if a table is causing this problem, run the following query against your database:

sp_msforeachtable 'exec sp_spaceused ''?'''

If you don't enable AWE on a 64bit server you can get errors like "A significant part of sql server process memory has been paged out. This may result in...

:hehe: I assume, you can't dig into the SQL code to see the cursordefinition ?

In that case, watch the process with profiler.

Otherwise, scan you code for phrases like

declare {name} cursor...

Try this procedure, which I developed (I will post it also in the scripts part of this website)

ALTER procedure [dbo].[usp_create_snapshot](@databasename sysname

, @SQLInstance varchar(10) = 'MSSQL.1'

, @debug bit = 0

, @verbose...

If you want to know howmany rows are processed by your cursor, query @@CURSOR_ROWS after you've opened the cursor. See the documentation for some pitfalls if you use this variable.

You need AWE to prevent memory stealing by the OS.

Also make sure you have a minimum and maximum size. Don't set the maximum size to unlimited, or SQL will...