sholliday (10/28/2010)

---

True, but BE WEARY of element based xml depending on your...

I see references to OPENXML in the postings.

Don't use OPENXML! Use XQuery. See the following SQL ServerCentral article:

http://www.sqlservercentral.com/blogs/michael_coles/archive/2008/01/20/stop-using-openxml-please.aspx

Mauve (11/9/2009)

---

Note that SQL Server 2005 Reporting Services has a bad defect related to linked reports. If the report is a linked report, the page size properties of the...

The same problem can occur in a standard web application where the Reporting Server is separate from the Database Server. Which it should be for performance, etc. I.e.,...

Having worked with Oracle for 25+ years, I'm continually frustrated with the lack of "core" functionality that Microsoft is so slow to implement. This is just another one as...

EdVassie (9/27/2010)

---

Interesting. Maybe the Microsoft documentation is wrong. See http://msdn.microsoft.com/en-us/library/ms345189.aspx for...

Not true. We successfully use Full-Text under SQL Server 2005 and SQL Server 2008 R2...

UMG Developer (6/25/2010)

---

I agree, but I think variable concatenation is very commonly used, so it is important for...

Hugo is 100% correct! Using this technique is 100% unpredictable. It will not work with table variables, derived tables, etc.

If you need to make a delimited list of...

Mighty (6/11/2010)

---

If the question was aiming at showing what the behaviour is of having "GO" in a batch, then it would have made sense to add the answer "The select...

sadair (6/9/2010)

---

Great article, thank you.

This will all work well when the delete is accomplished via the proc, but what happens when the delete is ad hoc from Enterprise Manager or...

christopher.cormier (6/9/2010)

---

This may be a faily easy quesion, but aside from the business requirement are there any performance benefits of putting the audit trail in a trigger? I'm fairly...

jacroberts (5/7/2010)

---

Grant Fritchey (5/7/2010)

---

Also, we make it a point of retaining the scripts that were generated for the final rollout to production, in case there's any question in the future...

bill page-320204 (5/6/2010)

---

Am I missing something here?

We use SourceSafe. We keep each proc separate. When I need to change one, I check it out, modify it, paste it...

No, it cannot be done in SQL Server 2005.

See the BOL: http://technet.microsoft.com/en-us/library/ms157399(SQL.90).aspx