fname lname-1111520 (12/2/2012)
I have not reported it. From briefly perusing the several thousand results on Connect for SQL Server and "csv", the standard cop-out for this issue seems to be "use SSIS import/export tools."
The fact that there is an option in SSMS to "quote strings containing list separators when saving .csv results" says everything.
"Interoperability with non-MS tools? We sure won't make it easy!"
Here is an amusing post on Connect regarding BCP: http://connect.microsoft.com/SQLServer/feedback/details/127032/bcp-utility-should-support-rfc-4180-csv-files
Ah... a kindred spirit!
I agree... why bother with feedback if the answer to many of the things you'd like to see is a referral to a tool that you don't want to use or can't use because of some restriction within the company? And, it IS a standard answer. SSIS doesn't always represent the needs of someone doing even simple ETL/File Import/Export of data stored in SQL Tables.
The other dangerous thing is that if they ever do an improvement based on feedback, they might deprecate something useful in the process. For example, I'm still scared to death that they'll deprecate xp_CmdShell in favor of the overcomplications of PowerShell. Don't get me wrong... PowerShell is a great tool for certain things. I just don't need it for simple file handling. I've still got lots of ETL code out there that keeps chugging away even though things like DTS went the wayside for SSIS, etc, ad infinitum.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs