TDS and character encodingThis is a discussion on TDS and character encoding within the Framework and Interface Programming forums in category; On Thu, 27 Sep 2007 08:54:30 -0700, bzh_29 <xiii29 @ free.Fr> wrote: >I've exactly the same trouble ... My apps is responding fine on a LAN >but when I goes on a WAN, getting horrible ! > >>From 5 sec to 7 min ... When I look SQL Time is the same so I look >network usage with network analyser and find the same result a you ! Just to make sure one basic point is covered, do all the stored procedures have SET NOCOUNT ON right at the beginning? Leaving that out can magnify network issues. Roy Harvey Beacon ... | ||||||||
| | ||||||||
| ||||||||
| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#61
09-28-2007, 09:34 AM
| |||
| |||
 Re: TDS and character encoding On Thu, 27 Sep 2007 08:54:30 -0700, bzh_29 <xiii29@free.Fr> wrote: >I've exactly the same trouble ... My apps is responding fine on a LAN >but when I goes on a WAN, getting horrible ! > >>From 5 sec to 7 min ... When I look SQL Time is the same so I look >network usage with network analyser and find the same result a you ! Just to make sure one basic point is covered, do all the stored procedures have SET NOCOUNT ON right at the beginning? Leaving that out can magnify network issues. Roy Harvey Beacon Falls, CT  |
|
#62
09-28-2007, 09:34 AM
| |||
| |||
| Re: TDS and character encoding On Thu, 27 Sep 2007 08:54:30 -0700, bzh_29 <xiii29@free.Fr> wrote: >I've exactly the same trouble ... My apps is responding fine on a LAN >but when I goes on a WAN, getting horrible ! > >>From 5 sec to 7 min ... When I look SQL Time is the same so I look >network usage with network analyser and find the same result a you ! Just to make sure one basic point is covered, do all the stored procedures have SET NOCOUNT ON right at the beginning? Leaving that out can magnify network issues. Roy Harvey Beacon Falls, CT |
|
#63
11-13-2008, 02:22 AM
| |||
| |||
| I don't know your business, but even if you are not aiming at the Far Eastern market, I don't know your business, but even if you are not aiming at the Far Eastern market, you may expand into Poland or Hungary one day. That's enough reason to use Unicode. Developing for Unicode from the start is cheap. Changing to Unicode after the fact is expensive. And if you use varchar in your application, what is really your problem? The only Unicode you need to send is the name of the stored procedures you call? Or are you sending query batches from the application? Now, if you do that, there are some bytes you can save by using stored procedures instead. |
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
All times are GMT -5. The time now is 03:17 AM.
