Your stated incrementation method is so unusual and customized that I'd suggest just creating table with pre-generated key values; and, when you need to increment by one, instead of...

SQLKnowItAll (3/22/2013)

IT is worth noting that we have 6 different environments and making sure all logins have a synced sid is sometimes not realistic. So that is why I...

SQLKnowItAll (3/22/2013)

---

ScottPletcher (3/22/2013)

---

SQLKnowItAll (3/22/2013)

---

ScottPletcher (3/22/2013)

---

IF you can very briefly drop the problem login(s) on your clients' machines, and immediately recreate them, you can fix this problem once and for all!...

SQLKnowItAll (3/22/2013)

---

ScottPletcher (3/22/2013)

---

IF you can very briefly drop the problem login(s) on your clients' machines, and immediately recreate them, you can fix this problem once and for all! Then...

IF you can very briefly drop the problem login(s) on your clients' machines, and immediately recreate them, you can fix this problem once and for all! Then you would...

frecal (3/21/2013)

---

Thanks Very much for this i was trying to also get it to work using this method (it is easier to follow). but get an error like

Msg 1033, Level...

Very little to go on ... but here's my best guess so far:

IF EXISTS(SELECT 1 FROM sys.objects WHERE name = 'FACT_SalesAnalysis')

DROP TABLE FACT_SalesAnalysis

-- ...

SELECT

DATEADD(HOUR, DATEDIFF(HOUR, 0, RunDateTime), 0) AS AvgHourlyDateTime,

--DATEADD(MILLISECOND, -3, DATEADD(HOUR, DATEDIFF(HOUR, 0, RunDateTime) + 1, 0)) AS AvgHourlyEndDateTime,

AVG([RowCount]) AS...

It looks to me like you're checking all connections to the database. If there are many such connections for different users, that could be a drag on the trigger.

So,...

Would need to also at least see the DDL ("CREATE TABLE"/"CREATE INDEX") for the tables, including all indexes.

You can use COALESCE(): for only 4 values, it's actually clearer to me personally (ymmv) than the other method.

SELECT

t.id,

COALESCE(t.field1, t.field2, t.field3, t.field4)...

Lynn Pettis (3/20/2013)

---

You do realize that shrinking a database will fragment the indexes used by the queries run to generate the reports and that this will impact the performance of...

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...