No.

When you...

Go look at the blog post again. Play with the example listed there if you need to. It's really not hard and it's explained in that blog post.

No.

DDL triggers are there to catch users making changes to the database.

Thanks

Sean Lange (9/23/2014)

---

Koen Verbeeck (9/23/2014)

---

Melanie.Townsend (9/23/2014)

---

I've just logged a request with the developers to see if they can have a look and see if we can get the points back....

dave 67553 (9/23/2014)

---

This would be from MSDN not a Developer Edition per se, and would not be used for production during normal use, but only if failed over to, which...

Unlikely. The people here know SQL Server, not MySQL, and for fixing database corruption you really need...

Meow Now (9/23/2014)

---

It gets quite frustrating when everything runs fine for months and then all of suddent some code takes a nose dive in performance, only in production at random...

Because the query plan that the optimiser generated there resulted in the data coming out in that order once the last query operators had finished with it.

There is NO guarantee...

Risk for shrinking files? What risk?

Any table over a single page could be spread across multiple files if there are multiple files in the filegroup.

You're already using dynamic SQL in your code. How can you say you're not allowed to do something you're already doing?

If you're using SQL 2008, the way you optimise this...

Tables are specific to a filegroup, not files. If there are multiple files in a filegroup, any table/index created on that filegroup will be spread across all the files in...

That job runs every hour, so if it...

Yup. Close on 3000 points.

No ORDER BY, no guarantee of order. End of story.

If you want a particular order, you put an ORDER BY. If you don't, you're telling SQL that it can return...