FYI, a FILLFACTOR of 80 is wasting space in many tables and perhaps even still have too little freespace in others.

You need to determine the best FILLFACTOR for each table...

Since the best plan will vary based on the selectivity of the specific @BatchID passed in, try it with the RECOMPILE option:

SELECT *

FROM <myDatabase>.<mySchema>.vw_BatchItems

WHERE BatchID = @BatchID

OPTION ( RECOMPILE );

No, that's not how those counters work.

A single SELECT statement can, and very often will, generate multiple physical reads.

A single UPDATE or DELETE statement can, and very often will, generate...

SELECT

'20130701' AS Date, Year,

6 AS JulyMaxhours,

SUM(6) AS Total_Hours,

KindOfDay, Month

FROM Auxiliary.Calendar

WHERE (KindOfDay =...

It's easy enough to generate the code for 00 to 99 based on the pattern for 00, so it's not really "manual" coding.

I figured on a (very broad) average of...

Not sure I fully understand, but maybe:

SELECT Date, Year, CASE DATEPART(mm, date) WHEN 07 THEN 6 END AS JulyMaxhours, KindOfDay, Month,

SUM(CASE WHEN DATEPART(mm, date) = 07 THEN 6 ELSE 0...

CREATE PROCEDURE [dbo].[GetExtractSiteExtractFileBatchPreviousSuccessInd]

@BatchStatusCd NVARCHAR(5)

,@ExtractSiteCd NVARCHAR(10)

,@ExtractAsOfDate DATETIME

AS

RETURN (

SELECT CASE

...

Maybe consider records to "match" if the SSN, first name and birth date all match. My reasoning: last name can change (marriage, etc.), and middle name may not be...

Or, depending on your specific needs, you could add your own logging/pseudotrace code to the proc itself, and trigger it with an optional parameter:

CREATE PROCEDURE dbo.proc_name

@...,

...

You don't really need SSMS to generate the statement. [And of course you don't try to make the change using SSMS, as SSMS will rebuild the entire table foe...

winmansoft, you should also be aware of the 14-byte-per-row overhead that READ_COMMITTED_SNAPSHOT requires. Anytime a row is updated, or a new row is inserted, the 14 bytes will be...

brettstahlman (3/18/2013)

---

Lynn Pettis (3/16/2013)

---

brettstahlman (3/16/2013)

---

Lynn Pettis (3/16/2013)

---

brettstahlman (3/16/2013)

---

opc.three (3/16/2013)

---

The reason why I disagree is because of the behavior of the after trigger when it is the instead trigger that is...

Could you go to NUMERIC(19,6)? That should work fine, and I think it will be just a metadata change.

This is off the wall, but did "AUTO_CLOSE" somehow get set on for that db?

That's a longshot, since even if it did it should auto_open when you reference it, but...

Interesting.

SSMS is probably internally running a query / stored proc to get the list of databases. Obviously the "SET ROWCOUNT" is affecting the code it uses as well.

I guess...