Thanks Paul.

>>2. SQL Server will only update statistics if they are potentially useful to the optimizer, and found to be out of date. Statistics that are never useful will never be...

Paul White NZ (3/25/2010)

---

There's no real harm in doing what they are asking, so it's hard to come up with a compelling argument not to do it.

My best shot would...

lmu92 (3/24/2010)

---

Maybe this argument will help, too:

Within one query, SQL server will only use one index per table. So, if you have the following query

SELECT col1, col2, col3, col4

FROM table

WHERE...

I will add that this certainly looks like this could be a quite complex problem. Forums, as someone else mentioned, are 'staffed' by volunteers and they are best used...

John Mitchell-245523 (3/23/2010)

---

This is one way of...

Richard M. (3/22/2010)

---

Idera's SQL Diagnostic Manager includes the SQL Mobile Manager that lets you do that and much more. Of course, it is a steep price if only or that...

Paul White NZ (3/24/2010)

---

Possibly because auto-shrink may compact data onto fewer pages?

edit: Jack...

Tom, why do you think that autoshrink will make the database more likely to fit into RAM?

If you want this new paging process to be even remotely efficient you WILL have to refactor it. In doing this many times for a variety of clients in...

One very important thing has been missed in this thread (and in Lynn's article from my quick review): error checking and explicit transaction begin/rollback/commit.

I also didn't see any mention...

1) What exactly is an INS backup?

2) What index maintenance is being done?

3) run dbcc sqlperf(logspace) and report the size and percent used on the tlog of the relevant database.

4)...

Also note that Microsoft recommends you do some homework to evaluate the system BEFORE you enable lock pages in memory because it can cause or exacerbate problems.

rgarrett 82118 (3/18/2010)

---

CREATE TABLE [dbo].[syQueueXMLMessage](

[TrackingNbr] [uniqueidentifier] NOT NULL,

[XMLMessage] [nvarchar](3000) NOT NULL,

[UserID] [int] NOT NULL,

[DateAdded] [datetime] NOT NULL,

[ts] [timestamp] NOT NULL,

CONSTRAINT [syQueueXMLMessage_TrackingNbr_U_C_IDX] PRIMARY KEY CLUSTERED

(

[TrackingNbr] ASC

)WITH (PAD_INDEX =...

almost certainly parameter sniffing on the initial query, wrong datatype, or widely disparate values leading to suboptimal plan in cache. There are ways to deal with each of those.