GilaMonster (11/3/2008)

---

Surprise surprise (not). Is it sharing drives...

TheSQLGuru (11/3/2008)

---

perf mon counters avg disk sec/read and avg disk sec/write for each individual drives should reveal such performance problems, as would examining the virtual files stats DMV (or fn_virtualfilestats,...

I should mention that, after moving the LOG file of the target db to a LUN physically located on the TEST SAN, performance was drastically improved from 12 to 6...

Thanks all, after reading through your replies, it doesn't seem worth it fiddling with the checkpoint frequency.

After more detailed analysis, this looks very much like a disk-performance (contention) issue.

As I...

Thanks, how can I configure it at the server level?

usman.tanveer (10/31/2008)

---

Thanks alot, this certainly is very useful information. Now what about 64 BIT? i am assuming that AWE is not required for 64 BIT, so how can i monitor...

gah (10/31/2008)

---

Thanks for the reply Marios

- enable AWE to max memory of 4 GB, to enable the data buffer of your SQL instance to 'see' 4 GB of memory and...

usman.tanveer (10/30/2008)

---

I have assinged max memory to 7 GB, so how can it be using 3 or 2 GB at max?

More over how can i find which switch is...

gah (10/30/2008)

---

Apologies if I should have created a new topic....

Having read thro this thread and a multitude of others on here and elsewhere, I must confess to still being confused....

We...

Then you are using at most 3 GB (if you have the 3-gb switch enabled) or 2 GB (if...

happycat59 (10/29/2008)

---

First - is the migration of data occurring in a single database transaction or multiple ? If it is a single transaction then you should expect that your...

usman.tanveer (10/29/2008)

---

My Problem is different......i have set the MAX MEMORY variable of SQL Server to 7GB. Now i want to know that out of this 7GB MAX MEMORY, how much...

The best medicine for parameter sniffing (in my experience) is a "UPDATE STATISTICS tblName WITH FULLSCAN" on all (large) tables involved.

The memory SQL server is currently consuming is not readily available, but you can get info on this indirectly by this counter:

Memory:Available Bytes

This is the memory available to new processes....

Also, gather some of your largest tables, those most actively queried in your system.

Do "sp_helpindex tblName" to get a list of indexes for each table.

Run "DBCC SHOW_STATISTICS ('tblName', 'idxName')" on...