You can't trust the database to enforce foreign keys anyway.

https://connect.microsoft.com/SQLServer/feedback/details/357419/merge-statement-bypasses-referential-integrity#details

😛 😀 😛

Ok. And RCS is a no-no because you can't modify the triggers, is that right?

Enterprise can be reasonably good at...

Yes - same one! It uses Extended Events (new in...

sumit.joshij (4/4/2010)

---

Ok.

the padded value should be like any systimatic value say (00001...00009.....00010....00100...001000) like that. in this it support/possible the reverse indexing. But in the auto incremented value the reverse...

MeltonDBA (4/4/2010)

---

I have not had a chance to use it but would be interested to hear if it works for you or not. The app was published on codeplex.com...

Marios Philippopoulos (4/4/2010)

---

One thing I find a little disconcerting with RCSI is the risk of non-repeatable reads, ie. the possibility that 2 SELECTs involving the same table within a transaction...

Marios Philippopoulos (4/4/2010)

---

The database code in our system is littered with NOLOCK hints, and we are considering switching to Read Committed Snapshot Isolation (RCSI) in the near future. Once...

david_wendelken (4/4/2010)

---

PaulB-TheOneAndOnly (4/4/2010)

---

david_wendelken (4/4/2010)

---

I start with the premise that the data is supposed to be valid. That's, on occasion, NOT a business requirement at all. (Sometimes the business...

Just checked the Quest site, and it appears that the latest release (5.2.0) does support the Cleanup History task. See http://www.quest.com/Quest_Site_Assets/PDF/LiteSpeed_520_ReleaseNotes.htm

For close-to-real-time reporting, I agree that transactional replication is a good choice.

Be sure to place the Distributor on the reporting server, not the production system.

Steve Jones - Editor (4/1/2010)

---

Log shipping...

sumit.joshij (4/3/2010)

---

While maintaining a database which values should we use as a PK. is it preferable to use auto incremented or our self generated padded values

say self generated Padded...

Continuing the theme Robert Miller started, if data readers can tolerate reading older data, also consider creating a database snapshot to implement the read-only access. This can work well...

Unless dynamic SQL is used 🙂

See:

High Availability Overview

SQL Server 2008 High Availability - Always On

White Paper: SQL Server 2008 High Availability - Always On Technologies

You can expect 3-5% higher CPU utilization.

The primary reason that the cost is so low is that...