Visual studio 2005 corrupt MS SQL 2000 stored procedures

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

DZanke@Yahoo.com - 29 Jun 2007 21:13 GMT

When our developers access a MS SQL 2000 stored procedure using Visual
Studio 2005, it seems to save the stored procs in a format that causes
problems w/ MS SQL 2000. When I view the stored proc w/ a binary
editor, there are all kinds of null characters and hex characters like
"FF FE" , This makes MS SQL 2000 enterprise manager choke & spit out
syntax errors. Has anyone heard of this? If so, any advice will be
much appreciated.

Reply to this Message

bruce barker - 29 Jun 2007 22:49 GMT

vs2005 will save the proc files as unicode. whatever you use to load
them into sql2000 probably does not handle unicode. in vs you can still
save as text (its an option, but must be done on each file).

-- bruce (sqlwork.com)

> When our developers access a MS SQL 2000 stored procedure using Visual
> Studio 2005, it seems to save the stored procs in a format that causes
[quoted text clipped - 3 lines]
> syntax errors. Has anyone heard of this? If so, any advice will be
> much appreciated.

Reply to this Message

David Z - 02 Jul 2007 21:49 GMT

This turned out to have nothing to do w/ MSSQL 2000 enterprise
manager, but the PC that is running Enterprise Manager. On 2 PCs
running the same version of Enterprise Manager, the same stored proc
source code will appear correctly and generate the stored proc
correctly on one, but not the other. This must have to do w/ a setting
in the registry that deals w/ unicode characters, but I have no idea
what it is.

Reply to this Message

Visual studio 2005 corrupt MS SQL 2000 stored procedures

Free Magazines