sql - Same code executed on different servers (same version) yields different results -


issue delphi legacy code. added 1 line of code correct 1 error , created new error.

new error causing same executable yield different results on different servers(switched pointer dev prod environment on executable).

code:

sescapedstring:=stringreplace(sstringin,'[','''+char(27)+''[',[rfreplaceall]); sescapedstring:=stringreplace(sescapedstring,']','''+char(27)+'']',[rfreplaceall]); sescapedstring:=stringreplace(sescapedstring,'''','''''',[rfreplaceall]);// line created new  bug result:=' ''' + trim(sescapedstring) + '%'''+'  escape char(27) ';

when running code against dev query finds objects characters '[' , ']' in against prod query not find items:

the first thing checked data: identical in both cases second thing checked sql server versions (11.0.3128 on both servers) third thing checking settings on servers: dbcc useroptions; -- same on both select name, collation_name sys.databases -- same on both select @@options -- same on both. quoted identifiers 'on' both servers

it comes down fact know 1 server treating escape character (chr(27)) differently other knot know why.

does have theory(or answer) why 2 similar servers treating escape characters differently?

the goal here getting prod server return values '[' , ']', setting system work legacy code take lot of additional time. have fix code 

sescapedstring:=stringreplace(sstringin,'[','[[]',[rfreplaceall]);

but faster option seem getting server read values same.

update: found root cause of difference , more mundane expected, turns out query running executed twice. second execution missing key piece on production server. issue resolved moving new line of code executed first rather last.

i first try find out if sql causes different behaviour when sent application: sending sql interactive sql client tool both servers.

to make sure manually tested sql same in application, try log or capture exact sql sent application text file , paste content sql client tool.

if server culprit, using sql different client tool should cause same difference 2 servers. if client tool shows same (correct) result on both servers, going on in delphi application.

p.s. upvoted, interesting phenomenon


Comments

Post a Comment

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

request animation frame stops working when exiting fullscreen clicking on original space's safari window. fine if fullscreen mode canceled escape key or calling cancelfullscreen(). steps reproduce: open https://dl.dropboxusercontent.com/u/769042/prezi/safari-fullscreen.html click "draw raf", kittie appears click "fullscreen", go fullscreen click "draw raf", kittie appears go space original safari was, showing "click exit fullscreen mode", click anywhere, out fullscreen click "draw raf", nothing happens what handling click calling: window.requestanimationframe(draw); which draws on canvas context: function draw() { ctx.drawimage(img, math.random()*500|0, math.random()*400|0, 100, 100); } i checked .hidden , .visibilitystate, updated correctly. tested on osx 10.9.3, safari 7.0.4 (9537.76.4). has workaround/solution other switching old settimeout? this sounds webkit bug 88940 : using reque...
Read more

jsf - How to ajax update an item in the footer of a PrimeFaces dataTable? -

this visual of table have: +---------+------------+-------------------+ | header1 | header2 | header3 | +---------+------------+-------------------+ | row | input | calc'ed output | | row b | input b | calc'ed output b | | etc.. | etc.. | etc.. | +---------+------------+-------------------+ | total: total calc'ed output | +------------------------------------------+ and stripped-down code: <p:datatable id="mytable" value="#{mybean.somelist}" var="currentitem"> <p:column headertext="header1"> <h:outputtext value="#{currentitem.name}" /> </p:column> <p:column headertext="header2"> <pe:inputnumber value="#{currentitem.inputval}"> <p:ajax event="change" listener="#{mybean.changelistener}" update="outputval outputtotal...
Read more

django - CSRF verification failed. Request aborted. CSRF cookie not set -

error: reason given failure: csrf cookie not set. in general, can occur when there genuine cross site request forgery, or when django's csrf mechanism has not been used correctly. post forms, need ensure: browser accepting cookies. view function uses requestcontext template, instead of context. in template, there {% csrf_token %} template tag inside each post form targets internal url. if not using csrfviewmiddleware, must use csrf_protect on views use csrf_token template tag, accept post data. you're seeing section of page because have debug = true in django settings file. change false, , initial error message displayed. can customize page using csrf_failure_view setting. did find, nothing helped, must foolish(( my template <form method="post">{% csrf_token %} {% field in form %} <div class="control-group"> {{ field }} </div> {% endfor %} <input type=...
Read more