Again:

The correct behavior for an aggregate concatenation query is undefined.

The vendor is not giving any guarantees, and this is the key issue.

Up to SQL Server 6.x GROUP BY implied an...

ksatpute123 (7/25/2013)

---

Following this I don't see any reason why GROUP BY over aggregate concatenation will not work in any scenario. So far I have never encountered an example of the...

If you have a CLR solution, looks like your main problem is your DBA.

Could you post the output from "SELECT @@version" for your server, as well information about the machine....

Sorry, it's far from clear what you are doing. But as I recall what you down load is a self-extracting package. Thus, once you have extracted the package, you need...

The article is certainly contradictive, but I've decided to let it stop with the first sentence:

The correct behavior for an aggregate concatenation query is undefined.

The article then goes out of...

The text for SET NOCOUNT ON, says: SET NOCOUNT ON prevents the sending of DONE_IN_PROC messages to the client for each statement in a stored procedure. DONEINPROC is generated in...

Why would it?

See this KB article Pay particular attention to the first sentence under Cause.

No. It should become a value > 5.

If you need consecutive numbers, you should not use...

See http://www.sommarskog.se/blobload.txt for a simple example.

Maybe you should keep the default as it is.

You could use user_id() and this returns sys.principals.principal_id. The value would not change if the database is moved to a different server....

Funny. And it only happens to views? What happens if you try to script these views?

SELECT substring(list, 1, len(list) - 1)

FROM (SELECT list =

(SELECT DISTINCT name + ','

...

In...

You wanted to convert to datetime, didn't you? Datetime is a binary value and includes no format. If you want a text string, just add a conversion to varchar. However,...

You got incorrect results. That's a bug.

Optimize for uknown may 'fix' the issue in this situation but...