I have been searching the forums for this issue and I haven't found anything on it so I apologize in advance if this issue has already been covered. My eyes are droopy and the coffee supply is low.

Is there a way to always save a file as UTF-8 or ANSI in SQL Server Management Studio? In analyzer you could save as ANSI, etc.

- d

Yep, that's possible:

1) Open the script
2) File > Save As...
3) Click on the little arrow on the right of the "Save" button
4) Select "Save with Encoding..."
5) Choose your encoding. Several varieties of UNICODE, double-width UNICODE, and a bunch of "single-byte" formats are available.

Hope this helps,
Steve

Yep, that's possible:

1) Open the script
2) File > Save As...
3) Click on the little arrow on the right of the "Save" button
4) Select "Save with Encoding..."
5) Choose your encoding. Several varieties of UNICODE, double-width UNICODE, and a bunch of "single-byte" formats are available.

Hope this helps,
Steve

Excellent, thank you.

Is there a way to make this the default save option?

Our source control doesnt handle unicode files very well and its a real pain to remember to change the default save option every time

Hi,

Originally I thought that my settings were saved, but once I opened mgt. studio again, I had to select the encoding again. This is annoying. If there is a setting somewhere that we can change to keep the encoding we choose as the default it would really help.

- d

That's very useful feedback. Could you please file a suggestion on http://connect.microsoft.com/SqlServer?

The product teams use customer feedback to help prioritize future work. Filing the suggestion on the Connect site does two things: First, it ensures that your suggestion goes directly into our internal issue tracking system and we don't lose any information. Second, suggestions from customers carry more weight than those proposed by employees, so filing suggestions on Connect can have a bigger impact on future improvements.

Thanks,
Steve

I also need this feature!

I will register as well.

Charlie.

I have also been hampered by this issue. I am glad to finally find this information. I did not see a feedback about setting the default encoding for the saving of SQL scripts, so I posted one myself.