July 21, 2015 at 9:26 am
Hello,
I recently migrated a production environment from a Windows 2003 server with SQL Server 2005 (SVPK 2). I migrated the environment to a Windows 2008 Server with SQL Server 2005 (SVPK 4).
Now, users are complaining about stranger characters on their web page. Of course, the DBA received a call.
I've checked:
Server collation
The particular database collation
The particular database compatibility level
The particular database recovery model
MSDB database collation
MODEL database collation
field collation
field character set name
field datatype
All are the same on both servers. I've noticed that one field value there is a "," in the old server, there is now a "->" on the new server. Any ideas what else could change the characters?
Thanks
Tony
Things will work out. Get back up, change some parameters and recode.
July 21, 2015 at 10:06 am
WebTechie (7/21/2015)
Hello,I recently migrated a production environment from a Windows 2003 server with SQL Server 2005 (SVPK 2). I migrated the environment to a Windows 2008 Server with SQL Server 2005 (SVPK 4).
Now, users are complaining about stranger characters on their web page. Of course, the DBA received a call.
I've checked:
Server collation
The particular database collation
The particular database compatibility level
The particular database recovery model
MSDB database collation
MODEL database collation
field collation
field character set name
field datatype
All are the same on both servers. I've noticed that one field value there is a "," in the old server, there is now a "->" on the new server. Any ideas what else could change the characters?
Thanks
Tony
Without seeing the data and without access to a Server 2003 or Server 2008 machine I would only be guessing. I used to be a web developer, however, and "->" looks like it could be a broken comment. <!-- comment here blah, blah --> There's a number of things that could cause that.
As a former DBA I would tell you to remember this: people call DBA's with all kinds of things that they can't figure out, even when it has nothing to do with the DBA. You're job is to determine if it's your code/data/server or not. Then a solution if it's your code/data/server... See if you can track the data from the database through it's journey from the DB to the web page.
When I troubleshoot this kind of thing I look at what data is being returned from the database first. If the application that is requesting the data is receiving the same data that it used to then the problem may not have to do with your data/server/code... Somewhere between the webpage and the data the data is changing. Since you don't (or shouldn't be required to) deal with IIS, ASP.NET, etc - solving this thing should be a team effort.
-- Itzik Ben-Gan 2001
July 21, 2015 at 1:16 pm
Yes, I know the database is always the problem to some.
However, I just wanted to give due diligence to the problem. Just in case there wasn't something else that I should have checked.
I created a spreadsheet to show that old server configurations and the new server configurations were the same.
Thanks for responding though.
Tony
Things will work out. Get back up, change some parameters and recode.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply