I prefer to name procedures first by topic area as well. I was merely pointing out that it's more common to use verb_object.

Personally I despise a prefix that represents...

Jeff Moden (8/17/2016)

---

ScottPletcher (8/17/2016)

---

Jeff Moden (8/16/2016)

---

ScottPletcher (8/16/2016)

---

Jeff Moden (8/16/2016)

---

ScottPletcher (8/16/2016)

---

Even so, it's likely that for in-house audits, or less formal audits, the current table could be freely accessed, and then...

Probably most common is verb_object, such as Get_UserName, or some such. I've never seen the "main" table name used as part of the proc name, and it seems like...

Jeff Moden (8/16/2016)

---

ScottPletcher (8/16/2016)

---

Jeff Moden (8/16/2016)

---

ScottPletcher (8/16/2016)

---

Even so, it's likely that for in-house audits, or less formal audits, the current table could be freely accessed, and then INSERTs might not...

Jeff Moden (8/16/2016)

---

ScottPletcher (8/16/2016)

---

Even so, it's likely that for in-house audits, or less formal audits, the current table could be freely accessed, and then INSERTs might not need logged. ...

Grant Fritchey (8/16/2016)

---

MyDoggieJessie (8/16/2016)

---

I've always been a little fuzzy on this one - So, is just executing sp_updatestats a safe bet after indexing? Realizing that rebuilildng indexes will only...

Even so, it's likely that for in-house audits, or less formal audits, the current table could be freely accessed, and then INSERTs might not need logged. But verify that...

Ed Wagner (8/16/2016)

---

ScottPletcher (8/16/2016)

---

Ed Wagner (8/16/2016)

---

ScottPletcher (8/16/2016)

---

Jeff Moden (8/15/2016)

---

ScottPletcher (8/15/2016)

---

Jeff Moden (8/15/2016)

---

ScottPletcher (8/15/2016)

---

Jeff Moden (8/15/2016)

---

Also, you should probably avoid auditing inserts. It's an unnecessary duplication of data because even...

Ed Wagner (8/16/2016)

---

ScottPletcher (8/16/2016)

---

Jeff Moden (8/15/2016)

---

ScottPletcher (8/15/2016)

---

Jeff Moden (8/15/2016)

---

ScottPletcher (8/15/2016)

---

Jeff Moden (8/15/2016)

---

Also, you should probably avoid auditing inserts. It's an unnecessary duplication of data because even if there's never...

Jeff Moden (8/15/2016)

---

ScottPletcher (8/15/2016)

---

Jeff Moden (8/15/2016)

---

ScottPletcher (8/15/2016)

---

Jeff Moden (8/15/2016)

---

Also, you should probably avoid auditing inserts. It's an unnecessary duplication of data because even if there's never an update, the...

Jeff Moden (8/15/2016)

---

ScottPletcher (8/15/2016)

---

Jeff Moden (8/15/2016)

---

Also, you should probably avoid auditing inserts. It's an unnecessary duplication of data because even if there's never an update, the original data lives...

DECLARE @user-id nchar(10)

SET @user-id = '001'

SELECT @user-id AS UserID, p.*, 'Prods This User Hasn''t Purchased' AS Message

FROM Prod_T p

LEFT OUTER JOIN User_Prod_T up ON up.UserID = @user-id AND up.ProdID =...

Jeff Moden (8/15/2016)

---

Also, you should probably avoid auditing inserts. It's an unnecessary duplication of data because even if there's never an update, the original data lives in the original...

I don't see any reason to conflate the last run with the next run. Also, when you query job activity, you need to include the session_id to make sure...

koteravindra (8/8/2016)

---

HI,

suppose if I have 3 columns in index with index order as ASC .

Emplid,deptid,Accountid

10 2 ...