Exproment (3/14/2014)

---

Hi,

We have requirements for future DWH system. One of the requirements is that 200 users(60 of which contantion) will build reports from the system. I need choose license and...

1) Did you look at the query plan?

2) Do you have any Foreign Keys in play?

3) Do you have any triggers on the table you are deleting from?

JayK (3/12/2014)

---

Hi Kevin,

Thanks for taking the time to reply - apreciated.

To address your questions below:

1.I could look at enabling the T2371 flag again for sure - I guess where I...

william.rees.howells (3/13/2014)

---

Does anybody know why I see absolutely no performance improvement when I spread my primary file group over 8 separate files on 8 separate disks, as opposed to...

JayK (3/12/2014)

---

Hi,

Just thought I would throw something out for discussion and perhaps see what other people out there are doing to see if I can be doing things better where...

If after your backup you run the select query TWICE or 3 or 4 times, does it return back to the original 4 second run time? If so, then...

search web for: log reuse wait desc replication sql server

Replication is an obvious possibility here. Can't flush out stuff if replication isn't satisfied for tlog'd stuff. Could also...

SQL_Student (3/11/2014)

---

Have queries which checks the scan density/ fragmentation of the indexes per table on db all seems fine there are one or two that's a bit fragmented but not...

SQL_Student (3/11/2014)

---

Merge and transactional replication has been setup (4 diff sites db's being replicated to a group database) few tables setup for transactional replication and a few tables setup for...

Minaz (3/8/2014)

---

Hi ,

We are having very big tables in TBS and wanted to setup a strategy for index maintenanace. PLease suggest best practices and approachees for this.

Thanking you for...

I am pretty sure the maintenance solution at ola.hallengren.com has the ability to turn off all messaging. Even if it doesn't you should still use it (for everything, not...

This is easy to do: upgrade to SQL Server 2014 and use a "Hekaton" in-memory table. 🙂 No locks/latches are taken there. I note that you need...

"It's always the little things" ... indeed it is!!! Glad you got your space back!

Or this (note: 3 part series here): http://blogs.msdn.com/bartd/archive/2006/09/09/Deadlock-Troubleshooting_2C00_-Part-1.aspx

Maddave (3/6/2014)

---

Many thanks for the reply. I am on build 11.0.3128. I've only applied the fix to the ms installer running bug as I experienced this a while back....