Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I recently migrated a database from MSDE 2000 to MSSQL 2005 that is used for a tourist website that can be displayed in one of three languages. A stored procedure is executed in ASP with a number that represents the language to use

When I run the stored procedure in SSMS, I don't get any errors although I have noticed that in Query Analyzer on the MSDE 2000 server I get 23 rows, where as in SQL Server 2005 SSMS I only get one big row.

This is the first time I've seen FOR XML EXPLICIT used so I don't have any experience with it.

Why is MSDE sending back 23 rows and SSMS only 1 big one

Any thing I need to configure in IIS to correctly display XML output coming from SQL Server ?

That query should return one row. Not sure what MSDE is doing. Does it return well-formed XML? I think there may be an issue with character encoding here, too.
–
Jon SeigelJan 9 '13 at 19:17

In SSMS, the XML looks well formed, its in IIS that I get all those Asian characters above.
–
Craig EfreinJan 10 '13 at 9:54

Okay, the issue is a character encoding issue then. XML is always 2 bytes per character, but if the application is expecting 1 byte per character, you get garbage output like that.
–
Jon SeigelJan 10 '13 at 14:09