SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


migrated to sql 2008 R2 from an old sql 2000 database using compatibility mode, some passwords don't...


migrated to sql 2008 R2 from an old sql 2000 database using compatibility mode, some passwords don't work anymore

Author
Message
stephen.hare
stephen.hare
SSC-Enthusiastic
SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)

Group: General Forum Members
Points: 151 Visits: 2
so here's the situation.

We use an old proprietary piece of software made in vb.net from a long time ago. We don't have the source code. We need this service for a few more months but we migrated to a new hosting provider who won't support sql 2000, so we put it on sql 2008 R2 with compatibility mode on for sql 2000. Everything seems fine except, the login from the app (using odbc) will fail if we put regular LOWER case characters (a,b,c,d,e,f...etc) in there. If we use numbers only and/or some non-ascii characters (I know - and ! and @ work fine) or even all upper case it works. I'm trying to figure out what's going on here, it just uses the SQL server login credential for access, any Ideas? I know the coalition is the same, I'm assuming it's something in the way sql 2008 is interpreting the connection. The ODBC connection using the same credentials itself works fine. Is there any way for me to capture the vb.net login when it passes the password?

I'm not a developer, I was a SQL dba in the past, but not for a few years, so my skills are extremely rusty. Please bear with me as I remember all my long forgotten techniques. I've tried all letters and they all fail.

any ideas would be great. If you need me to put any info in here, just let me know what.

thanks,

-Steve Hare
John Mitchell-245523
John Mitchell-245523
SSC Guru
SSC Guru (122K reputation)SSC Guru (122K reputation)SSC Guru (122K reputation)SSC Guru (122K reputation)SSC Guru (122K reputation)SSC Guru (122K reputation)SSC Guru (122K reputation)SSC Guru (122K reputation)

Group: General Forum Members
Points: 122502 Visits: 18761
stephen.hare - Wednesday, February 15, 2017 8:49 AM
Everything seems fine except, the login from the app (using odbc) will fail if we put regular LOWER case characters (a,b,c,d,e,f...etc) in there.

Steve

In where? I don't really understand. Is the login and/or password hard-coded in the application? Are you saying you don't have access to either or both of them? Is the login set up on the new server?

If I remember correctly, SQL login passwords in SQL Server 2000 were only case-sensitive if the server collation was case-sensitive.

John

stephen.hare
stephen.hare
SSC-Enthusiastic
SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)

Group: General Forum Members
Points: 151 Visits: 2
HI John,

thanks for replying. the Login isn't hardcoded, when you open the .exe it first prompts for a user and password, then passes those on (assuming through the ODBC) and authenticates against the sql server login.

I know the sql server login itself is fine, as I've tested outside the app, one quirk, when I cut and paste a password (even lower case letters) it works fine, it's only when you try to type the password and it contains lower case letters. Very odd. And this exact same app. works fine when authenticating against a copy of the db living on sql 2000.
John Mitchell-245523
John Mitchell-245523
SSC Guru
SSC Guru (122K reputation)SSC Guru (122K reputation)SSC Guru (122K reputation)SSC Guru (122K reputation)SSC Guru (122K reputation)SSC Guru (122K reputation)SSC Guru (122K reputation)SSC Guru (122K reputation)

Group: General Forum Members
Points: 122502 Visits: 18761
At a guess, I'd say the application is converting the password to upper case, which wouldn't have mattered on SQL Server 2000 (depending on the server collation) but definitely does matter on all later versions. Looks like you're going to need to choose a password with numeric, special and upper case only.

John
Erland Sommarskog
Erland Sommarskog
SSCoach
SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)SSCoach (19K reputation)

Group: General Forum Members
Points: 19828 Visits: 883
I can confirm what John says about the password. On SQL 2000, passwords were case-insensitive, if the server collation was case-insensitive. This was changed in SQL 2005.

If the application uppercasess all letters, that sounds a little crazy, but I have no alternative explantion to offer.

Erland Sommarskog, SQL Server MVP, www.sommarskog.se
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search