I have a server that uses specific login/passwords. And through random
testing i noticed that the passwords are not case sensitive. Can this be
changed so that the passwords ARE case sensitive?
thanks,
BenHi,
For a Case insensitive sort order/carecter set it is not possible. If you
have a Case sensitive sortorder/char set then automatically
passwords will be case sensitive.
Thanks
Hari
SQL Server MVP
"Ben" <ben_1_ AT hotmail DOT com> wrote in message
news:0E632896-37E7-4EA0-8022-5AC2D4230F84@.microsoft.com...
>I have a server that uses specific login/passwords. And through random
> testing i noticed that the passwords are not case sensitive. Can this be
> changed so that the passwords ARE case sensitive?
> thanks,
> Ben|||SQL Server 2000 maintains two versions of each login password. One is the
actual password supplied by the user, and the other is the password
converted by to all uppercase letters. This enables case-insensitive
validation of passwords (for case insensitive collations). Although this
behavior is convenient for many users, it makes password-guessing attacks
easier by reducing the number of possible passwords
In SQL 2005 only the actual password is stored. A password entered by a user
must match the password stored in the server (regardless of collation,
however the username can still be in a different case). If a password does
not match the password stored in SQL Server, the login fails. If the precise
case of the password characters is forgotten, the password must be reset.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Ben" <ben_1_ AT hotmail DOT com> wrote in message
news:0E632896-37E7-4EA0-8022-5AC2D4230F84@.microsoft.com...
>I have a server that uses specific login/passwords. And through random
> testing i noticed that the passwords are not case sensitive. Can this be
> changed so that the passwords ARE case sensitive?
> thanks,
> Ben|||Hi,
Actually it because of *Collation setting* look for your collation and
change it accordingly to case sensitive from case insensitive .
Regards
--
Andy Davis
Activecrypt Team
---
SQL Server Encryption Software
http://www.activecrypt.com
"Ben" wrote:
> I have a server that uses specific login/passwords. And through random
> testing i noticed that the passwords are not case sensitive. Can this be
> changed so that the passwords ARE case sensitive?
> thanks,
> Ben
Showing posts with label case. Show all posts
Showing posts with label case. Show all posts
Monday, March 12, 2012
Password's case sensitivity
Hi,
somehow my Sql Server's passwors are not case sensitive. I thought sql
server's login passwords are case sensitive.
Am I worng?
How do I change my SQL Server back to the case sensitive passwords?
Please help..
Thank you
SamHi
Passwords case sensitivity is based on the collation of the installation. If
you install with a non-case sensitive collation, the password will not be
cases sensitive.
Regards
Mike
"sam" wrote:
> Hi,
> somehow my Sql Server's passwors are not case sensitive. I thought sql
> server's login passwords are case sensitive.
> Am I worng?
> How do I change my SQL Server back to the case sensitive passwords?
> Please help..
> Thank you
> Sam|||Password case-sensitivity is determined by the default collation for the SQL
Server instance. It appears you have a case-insensitive collation.
Hope this helps.
Dan Guzman
SQL Server MVP
"sam" <sam@.discussions.microsoft.com> wrote in message
news:BDB6FA4B-D047-438F-A850-0E3FD0A8F49B@.microsoft.com...
> Hi,
> somehow my Sql Server's passwors are not case sensitive. I thought sql
> server's login passwords are case sensitive.
> Am I worng?
> How do I change my SQL Server back to the case sensitive passwords?
> Please help..
> Thank you
> Sam|||Thank you for your response. I think the Earlier I used all the SQL servers
which are upgraded from 7.0 to 2K and so the defautl collation of 7.0 was a
case sensitive. (Not usre right now).
But if I want to keep all my client data and other code to be case
-insensitive but all my login passwords to be case sensitive , can I do that
?
How can I do that?
Please let me know..
Thank you again..
Sam
"Dan Guzman" wrote:
> Password case-sensitivity is determined by the default collation for the S
QL
> Server instance. It appears you have a case-insensitive collation.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "sam" <sam@.discussions.microsoft.com> wrote in message
> news:BDB6FA4B-D047-438F-A850-0E3FD0A8F49B@.microsoft.com...
>
>|||To change the instance default collation after installation, you'll need to
either reinstall or rebuild the master database. This will create new
master, msdb and model databases.
Although you can run with mixed collations, this can lead to problems. The
tempdb collation will be the instance default so you might get errors due to
collation conflicts when using temp tables.
Hope this helps.
Dan Guzman
SQL Server MVP
"sam" <sam@.discussions.microsoft.com> wrote in message
news:96622B87-A747-4E23-8593-27221C2C10BD@.microsoft.com...[vbcol=seagreen]
> Thank you for your response. I think the Earlier I used all the SQL
> servers
> which are upgraded from 7.0 to 2K and so the defautl collation of 7.0 was
> a
> case sensitive. (Not usre right now).
> But if I want to keep all my client data and other code to be case
> -insensitive but all my login passwords to be case sensitive , can I do
> that?
> How can I do that?
> Please let me know..
> Thank you again..
> Sam
> "Dan Guzman" wrote:
>|||Thanks Dan,
But I think I did not put my question clearly. My Apologies.
I want to keep the collation of all the DBs on the server same as what I
have at present (case in-sensitive) but only all my login passwords should b
e
case sensitive.
Can I do that?
How?
Thank you
Sam
"Dan Guzman" wrote:
> To change the instance default collation after installation, you'll need t
o
> either reinstall or rebuild the master database. This will create new
> master, msdb and model databases.
> Although you can run with mixed collations, this can lead to problems. Th
e
> tempdb collation will be the instance default so you might get errors due
to
> collation conflicts when using temp tables.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "sam" <sam@.discussions.microsoft.com> wrote in message
> news:96622B87-A747-4E23-8593-27221C2C10BD@.microsoft.com...
>
>|||Running mixed collations is the only way to have case-sensitive passwords
and case-insensitive user database collations. The default collation of
your existing databases will not be changed after you reattach following a
master database rebuild or SQL Server reinstall.
However, as I mentioned in my previous response, mixed collations will have
other consequences. If you feel compelled to try this, be sure to
thoroughly test your applications before implementing this in production.
Hope this helps.
Dan Guzman
SQL Server MVP
"sam" <sam@.discussions.microsoft.com> wrote in message
news:B4EB814F-DCAD-4AF1-AB66-11C821BFD09D@.microsoft.com...[vbcol=seagreen]
> Thanks Dan,
> But I think I did not put my question clearly. My Apologies.
> I want to keep the collation of all the DBs on the server same as what I
> have at present (case in-sensitive) but only all my login passwords should
> be
> case sensitive.
> Can I do that?
> How?
> Thank you
> Sam
> "Dan Guzman" wrote:
>|||I understand your concern and thank you for your response.
Bu insterad of rebuilding my master database, Can I change the collation of
the password column of the sysxlogin table?
This is just a guess. I think you must have thought of this but I still want
to ask you this question.
"Dan Guzman" wrote:
> Running mixed collations is the only way to have case-sensitive passwords
> and case-insensitive user database collations. The default collation of
> your existing databases will not be changed after you reattach following a
> master database rebuild or SQL Server reinstall.
> However, as I mentioned in my previous response, mixed collations will hav
e
> other consequences. If you feel compelled to try this, be sure to
> thoroughly test your applications before implementing this in production.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "sam" <sam@.discussions.microsoft.com> wrote in message
> news:B4EB814F-DCAD-4AF1-AB66-11C821BFD09D@.microsoft.com...
>
>|||> Bu insterad of rebuilding my master database, Can I change the collation
> of
> the password column of the sysxlogin table?
Changing system table schema is not supported so you would this is at your
own risk. The supported method is a mixed collation environment with a
case-sensitive instance default collation and case-insensitive collation for
user databases. Of course, mixed collation caveats apply.
Hope this helps.
Dan Guzman
SQL Server MVP
"sam" <sam@.discussions.microsoft.com> wrote in message
news:D516F2B3-79BF-414E-B005-88AB683F5DD5@.microsoft.com...[vbcol=seagreen]
>I understand your concern and thank you for your response.
> Bu insterad of rebuilding my master database, Can I change the collation
> of
> the password column of the sysxlogin table?
> This is just a guess. I think you must have thought of this but I still
> want
> to ask you this question.
> "Dan Guzman" wrote:
>|||Thank you Dan,
I will try this in the development environment and then see how it works
before changing the collation for any thing else.
Thank you once again for your time and response.
Sam
"Dan Guzman" wrote:
> Changing system table schema is not supported so you would this is at your
> own risk. The supported method is a mixed collation environment with a
> case-sensitive instance default collation and case-insensitive collation f
or
> user databases. Of course, mixed collation caveats apply.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "sam" <sam@.discussions.microsoft.com> wrote in message
> news:D516F2B3-79BF-414E-B005-88AB683F5DD5@.microsoft.com...
>
>
somehow my Sql Server's passwors are not case sensitive. I thought sql
server's login passwords are case sensitive.
Am I worng?
How do I change my SQL Server back to the case sensitive passwords?
Please help..
Thank you
SamHi
Passwords case sensitivity is based on the collation of the installation. If
you install with a non-case sensitive collation, the password will not be
cases sensitive.
Regards
Mike
"sam" wrote:
> Hi,
> somehow my Sql Server's passwors are not case sensitive. I thought sql
> server's login passwords are case sensitive.
> Am I worng?
> How do I change my SQL Server back to the case sensitive passwords?
> Please help..
> Thank you
> Sam|||Password case-sensitivity is determined by the default collation for the SQL
Server instance. It appears you have a case-insensitive collation.
Hope this helps.
Dan Guzman
SQL Server MVP
"sam" <sam@.discussions.microsoft.com> wrote in message
news:BDB6FA4B-D047-438F-A850-0E3FD0A8F49B@.microsoft.com...
> Hi,
> somehow my Sql Server's passwors are not case sensitive. I thought sql
> server's login passwords are case sensitive.
> Am I worng?
> How do I change my SQL Server back to the case sensitive passwords?
> Please help..
> Thank you
> Sam|||Thank you for your response. I think the Earlier I used all the SQL servers
which are upgraded from 7.0 to 2K and so the defautl collation of 7.0 was a
case sensitive. (Not usre right now).
But if I want to keep all my client data and other code to be case
-insensitive but all my login passwords to be case sensitive , can I do that
?
How can I do that?
Please let me know..
Thank you again..
Sam
"Dan Guzman" wrote:
> Password case-sensitivity is determined by the default collation for the S
QL
> Server instance. It appears you have a case-insensitive collation.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "sam" <sam@.discussions.microsoft.com> wrote in message
> news:BDB6FA4B-D047-438F-A850-0E3FD0A8F49B@.microsoft.com...
>
>|||To change the instance default collation after installation, you'll need to
either reinstall or rebuild the master database. This will create new
master, msdb and model databases.
Although you can run with mixed collations, this can lead to problems. The
tempdb collation will be the instance default so you might get errors due to
collation conflicts when using temp tables.
Hope this helps.
Dan Guzman
SQL Server MVP
"sam" <sam@.discussions.microsoft.com> wrote in message
news:96622B87-A747-4E23-8593-27221C2C10BD@.microsoft.com...[vbcol=seagreen]
> Thank you for your response. I think the Earlier I used all the SQL
> servers
> which are upgraded from 7.0 to 2K and so the defautl collation of 7.0 was
> a
> case sensitive. (Not usre right now).
> But if I want to keep all my client data and other code to be case
> -insensitive but all my login passwords to be case sensitive , can I do
> that?
> How can I do that?
> Please let me know..
> Thank you again..
> Sam
> "Dan Guzman" wrote:
>|||Thanks Dan,
But I think I did not put my question clearly. My Apologies.
I want to keep the collation of all the DBs on the server same as what I
have at present (case in-sensitive) but only all my login passwords should b
e
case sensitive.
Can I do that?
How?
Thank you
Sam
"Dan Guzman" wrote:
> To change the instance default collation after installation, you'll need t
o
> either reinstall or rebuild the master database. This will create new
> master, msdb and model databases.
> Although you can run with mixed collations, this can lead to problems. Th
e
> tempdb collation will be the instance default so you might get errors due
to
> collation conflicts when using temp tables.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "sam" <sam@.discussions.microsoft.com> wrote in message
> news:96622B87-A747-4E23-8593-27221C2C10BD@.microsoft.com...
>
>|||Running mixed collations is the only way to have case-sensitive passwords
and case-insensitive user database collations. The default collation of
your existing databases will not be changed after you reattach following a
master database rebuild or SQL Server reinstall.
However, as I mentioned in my previous response, mixed collations will have
other consequences. If you feel compelled to try this, be sure to
thoroughly test your applications before implementing this in production.
Hope this helps.
Dan Guzman
SQL Server MVP
"sam" <sam@.discussions.microsoft.com> wrote in message
news:B4EB814F-DCAD-4AF1-AB66-11C821BFD09D@.microsoft.com...[vbcol=seagreen]
> Thanks Dan,
> But I think I did not put my question clearly. My Apologies.
> I want to keep the collation of all the DBs on the server same as what I
> have at present (case in-sensitive) but only all my login passwords should
> be
> case sensitive.
> Can I do that?
> How?
> Thank you
> Sam
> "Dan Guzman" wrote:
>|||I understand your concern and thank you for your response.
Bu insterad of rebuilding my master database, Can I change the collation of
the password column of the sysxlogin table?
This is just a guess. I think you must have thought of this but I still want
to ask you this question.
"Dan Guzman" wrote:
> Running mixed collations is the only way to have case-sensitive passwords
> and case-insensitive user database collations. The default collation of
> your existing databases will not be changed after you reattach following a
> master database rebuild or SQL Server reinstall.
> However, as I mentioned in my previous response, mixed collations will hav
e
> other consequences. If you feel compelled to try this, be sure to
> thoroughly test your applications before implementing this in production.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "sam" <sam@.discussions.microsoft.com> wrote in message
> news:B4EB814F-DCAD-4AF1-AB66-11C821BFD09D@.microsoft.com...
>
>|||> Bu insterad of rebuilding my master database, Can I change the collation
> of
> the password column of the sysxlogin table?
Changing system table schema is not supported so you would this is at your
own risk. The supported method is a mixed collation environment with a
case-sensitive instance default collation and case-insensitive collation for
user databases. Of course, mixed collation caveats apply.
Hope this helps.
Dan Guzman
SQL Server MVP
"sam" <sam@.discussions.microsoft.com> wrote in message
news:D516F2B3-79BF-414E-B005-88AB683F5DD5@.microsoft.com...[vbcol=seagreen]
>I understand your concern and thank you for your response.
> Bu insterad of rebuilding my master database, Can I change the collation
> of
> the password column of the sysxlogin table?
> This is just a guess. I think you must have thought of this but I still
> want
> to ask you this question.
> "Dan Guzman" wrote:
>|||Thank you Dan,
I will try this in the development environment and then see how it works
before changing the collation for any thing else.
Thank you once again for your time and response.
Sam
"Dan Guzman" wrote:
> Changing system table schema is not supported so you would this is at your
> own risk. The supported method is a mixed collation environment with a
> case-sensitive instance default collation and case-insensitive collation f
or
> user databases. Of course, mixed collation caveats apply.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "sam" <sam@.discussions.microsoft.com> wrote in message
> news:D516F2B3-79BF-414E-B005-88AB683F5DD5@.microsoft.com...
>
>
passwords are case sensitive in 2005
Can we change the SQL passwords in 2005 to be case insensitive ?
ThanksNo...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Hassan" <hassan@.hotmail.com> wrote in message news:elz9A0Q6HHA.5980@.TK2MSFTNGP04.phx.gbl...
> Can we change the SQL passwords in 2005 to be case insensitive ?
> Thanks
>
ThanksNo...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Hassan" <hassan@.hotmail.com> wrote in message news:elz9A0Q6HHA.5980@.TK2MSFTNGP04.phx.gbl...
> Can we change the SQL passwords in 2005 to be case insensitive ?
> Thanks
>
Password: case sensitive
I installed SQL 2000 with default sort order. I though the password for SQL
logins is case-sensitive but it is not. Is that correct?
Thanks.Yes ...the passwords are not case sensitive... because of the collation
level . I beleive you might be able to change the collation for the password
column in sysxlogins table. Not tried it out but might be interesting if it
can be done
<Flicker> wrote in message news:OGqSaLqkDHA.708@.TK2MSFTNGP10.phx.gbl...
> I installed SQL 2000 with default sort order. I though the password for
SQL
> logins is case-sensitive but it is not. Is that correct?
> Thanks.
>
logins is case-sensitive but it is not. Is that correct?
Thanks.Yes ...the passwords are not case sensitive... because of the collation
level . I beleive you might be able to change the collation for the password
column in sysxlogins table. Not tried it out but might be interesting if it
can be done
<Flicker> wrote in message news:OGqSaLqkDHA.708@.TK2MSFTNGP10.phx.gbl...
> I installed SQL 2000 with default sort order. I though the password for
SQL
> logins is case-sensitive but it is not. Is that correct?
> Thanks.
>
Saturday, February 25, 2012
password case seasitive configuration
Hi, All,
I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
sql 2005 data, but the password is case seasitive. The sql 2000 is not case
seasitive, anyone knows we can configure sql 2005 user password is not
seasitive?
Thanks for your time,
MartinTo the best of my knowledge, you cannot change to case insensitive passwords in 2005. This behavior
change is documented in:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"martin1" <martin1@.discussions.microsoft.com> wrote in message
news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
> Hi, All,
> I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
> sql 2005 data, but the password is case seasitive. The sql 2000 is not case
> seasitive, anyone knows we can configure sql 2005 user password is not
> seasitive?
> Thanks for your time,
> Martin|||Hi, Tibor Karaszi,
1) if not in Sql 2005, do you know we can configute IIS web server is not
case seasitive?
2) where to see
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ? can you tell how to go there.
Thanks in advance,
Martin
"Tibor Karaszi" wrote:
> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This behavior
> change is documented in:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
> > Hi, All,
> >
> > I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
> > sql 2005 data, but the password is case seasitive. The sql 2000 is not case
> > seasitive, anyone knows we can configure sql 2005 user password is not
> > seasitive?
> >
> > Thanks for your time,
> > Martin
>|||1: SQL Server 2000 and earlier: Whether a password is case sensitive or not is determined by the
collation for the system databases (AFAIK), which was decided when you installed the SQL Server
instances. To change this, you need to use rebuildm.exe which will scratch all the system databases,
and should be performed unless you have good knowledge of the SQL Server architecture and can
determine what such a rebuild will do.
2: This is an URL for the Books Online that comes with SQL Server 2005. It is installed when you
install 2005, and you find an like in the SQL Server program group.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"martin1" <martin1@.discussions.microsoft.com> wrote in message
news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...
> Hi, Tibor Karaszi,
> 1) if not in Sql 2005, do you know we can configute IIS web server is not
> case seasitive?
> 2) where to see
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ? can
> you tell how to go there.
> Thanks in advance,
> Martin
>
> "Tibor Karaszi" wrote:
>> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This
>> behavior
>> change is documented in:
>> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "martin1" <martin1@.discussions.microsoft.com> wrote in message
>> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
>> > Hi, All,
>> >
>> > I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
>> > sql 2005 data, but the password is case seasitive. The sql 2000 is not case
>> > seasitive, anyone knows we can configure sql 2005 user password is not
>> > seasitive?
>> >
>> > Thanks for your time,
>> > Martin
>>|||Hi, Tibor Karaszi,
yuo mean sql server case seasitive can be changed by rebuidm.exe, this is
for sql 2000 or sql 2005?
Thanks
"Tibor Karaszi" wrote:
> 1: SQL Server 2000 and earlier: Whether a password is case sensitive or not is determined by the
> collation for the system databases (AFAIK), which was decided when you installed the SQL Server
> instances. To change this, you need to use rebuildm.exe which will scratch all the system databases,
> and should be performed unless you have good knowledge of the SQL Server architecture and can
> determine what such a rebuild will do.
> 2: This is an URL for the Books Online that comes with SQL Server 2005. It is installed when you
> install 2005, and you find an like in the SQL Server program group.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...
> > Hi, Tibor Karaszi,
> >
> > 1) if not in Sql 2005, do you know we can configute IIS web server is not
> > case seasitive?
> > 2) where to see
> > ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ? can
> > you tell how to go there.
> >
> > Thanks in advance,
> > Martin
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This
> >> behavior
> >> change is documented in:
> >> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> >> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
> >> > Hi, All,
> >> >
> >> > I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
> >> > sql 2005 data, but the password is case seasitive. The sql 2000 is not case
> >> > seasitive, anyone knows we can configure sql 2005 user password is not
> >> > seasitive?
> >> >
> >> > Thanks for your time,
> >> > Martin
> >>
> >>
>|||That only applies to 2000, logins are *always* case sensitive in 2005.
If you want to try this (2000): Make sure you test this on a test server first, as I'm not 100%
positive. But be aware that rebuildm does *a lot* of other things as well (it is pretty close to a
re-install). This is why I mentioned that you should be very familiar with what rebuildm does and
the consequences to running it, etc, before attempting this.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"martin1" <martin1@.discussions.microsoft.com> wrote in message
news:BF694D38-6032-4598-9CB6-4042F7D6BFC0@.microsoft.com...
> Hi, Tibor Karaszi,
> yuo mean sql server case seasitive can be changed by rebuidm.exe, this is
> for sql 2000 or sql 2005?
> Thanks
> "Tibor Karaszi" wrote:
>> 1: SQL Server 2000 and earlier: Whether a password is case sensitive or not is determined by the
>> collation for the system databases (AFAIK), which was decided when you installed the SQL Server
>> instances. To change this, you need to use rebuildm.exe which will scratch all the system
>> databases,
>> and should be performed unless you have good knowledge of the SQL Server architecture and can
>> determine what such a rebuild will do.
>> 2: This is an URL for the Books Online that comes with SQL Server 2005. It is installed when you
>> install 2005, and you find an like in the SQL Server program group.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "martin1" <martin1@.discussions.microsoft.com> wrote in message
>> news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...
>> > Hi, Tibor Karaszi,
>> >
>> > 1) if not in Sql 2005, do you know we can configute IIS web server is not
>> > case seasitive?
>> > 2) where to see
>> > ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ?
>> > can
>> > you tell how to go there.
>> >
>> > Thanks in advance,
>> > Martin
>> >
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This
>> >> behavior
>> >> change is documented in:
>> >> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://www.solidqualitylearning.com/
>> >>
>> >>
>> >> "martin1" <martin1@.discussions.microsoft.com> wrote in message
>> >> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
>> >> > Hi, All,
>> >> >
>> >> > I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
>> >> > sql 2005 data, but the password is case seasitive. The sql 2000 is not case
>> >> > seasitive, anyone knows we can configure sql 2005 user password is not
>> >> > seasitive?
>> >> >
>> >> > Thanks for your time,
>> >> > Martin
>> >>
>> >>
>>|||Thank you so much!
Martin
"Tibor Karaszi" wrote:
> That only applies to 2000, logins are *always* case sensitive in 2005.
> If you want to try this (2000): Make sure you test this on a test server first, as I'm not 100%
> positive. But be aware that rebuildm does *a lot* of other things as well (it is pretty close to a
> re-install). This is why I mentioned that you should be very familiar with what rebuildm does and
> the consequences to running it, etc, before attempting this.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:BF694D38-6032-4598-9CB6-4042F7D6BFC0@.microsoft.com...
> > Hi, Tibor Karaszi,
> >
> > yuo mean sql server case seasitive can be changed by rebuidm.exe, this is
> > for sql 2000 or sql 2005?
> >
> > Thanks
> >
> > "Tibor Karaszi" wrote:
> >
> >> 1: SQL Server 2000 and earlier: Whether a password is case sensitive or not is determined by the
> >> collation for the system databases (AFAIK), which was decided when you installed the SQL Server
> >> instances. To change this, you need to use rebuildm.exe which will scratch all the system
> >> databases,
> >> and should be performed unless you have good knowledge of the SQL Server architecture and can
> >> determine what such a rebuild will do.
> >>
> >> 2: This is an URL for the Books Online that comes with SQL Server 2005. It is installed when you
> >> install 2005, and you find an like in the SQL Server program group.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> >> news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...
> >> > Hi, Tibor Karaszi,
> >> >
> >> > 1) if not in Sql 2005, do you know we can configute IIS web server is not
> >> > case seasitive?
> >> > 2) where to see
> >> > ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ?
> >> > can
> >> > you tell how to go there.
> >> >
> >> > Thanks in advance,
> >> > Martin
> >> >
> >> >
> >> > "Tibor Karaszi" wrote:
> >> >
> >> >> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This
> >> >> behavior
> >> >> change is documented in:
> >> >> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
> >> >>
> >> >> --
> >> >> Tibor Karaszi, SQL Server MVP
> >> >> http://www.karaszi.com/sqlserver/default.asp
> >> >> http://www.solidqualitylearning.com/
> >> >>
> >> >>
> >> >> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> >> >> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
> >> >> > Hi, All,
> >> >> >
> >> >> > I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
> >> >> > sql 2005 data, but the password is case seasitive. The sql 2000 is not case
> >> >> > seasitive, anyone knows we can configure sql 2005 user password is not
> >> >> > seasitive?
> >> >> >
> >> >> > Thanks for your time,
> >> >> > Martin
> >> >>
> >> >>
> >>
> >>
>
I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
sql 2005 data, but the password is case seasitive. The sql 2000 is not case
seasitive, anyone knows we can configure sql 2005 user password is not
seasitive?
Thanks for your time,
MartinTo the best of my knowledge, you cannot change to case insensitive passwords in 2005. This behavior
change is documented in:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"martin1" <martin1@.discussions.microsoft.com> wrote in message
news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
> Hi, All,
> I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
> sql 2005 data, but the password is case seasitive. The sql 2000 is not case
> seasitive, anyone knows we can configure sql 2005 user password is not
> seasitive?
> Thanks for your time,
> Martin|||Hi, Tibor Karaszi,
1) if not in Sql 2005, do you know we can configute IIS web server is not
case seasitive?
2) where to see
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ? can you tell how to go there.
Thanks in advance,
Martin
"Tibor Karaszi" wrote:
> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This behavior
> change is documented in:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
> > Hi, All,
> >
> > I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
> > sql 2005 data, but the password is case seasitive. The sql 2000 is not case
> > seasitive, anyone knows we can configure sql 2005 user password is not
> > seasitive?
> >
> > Thanks for your time,
> > Martin
>|||1: SQL Server 2000 and earlier: Whether a password is case sensitive or not is determined by the
collation for the system databases (AFAIK), which was decided when you installed the SQL Server
instances. To change this, you need to use rebuildm.exe which will scratch all the system databases,
and should be performed unless you have good knowledge of the SQL Server architecture and can
determine what such a rebuild will do.
2: This is an URL for the Books Online that comes with SQL Server 2005. It is installed when you
install 2005, and you find an like in the SQL Server program group.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"martin1" <martin1@.discussions.microsoft.com> wrote in message
news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...
> Hi, Tibor Karaszi,
> 1) if not in Sql 2005, do you know we can configute IIS web server is not
> case seasitive?
> 2) where to see
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ? can
> you tell how to go there.
> Thanks in advance,
> Martin
>
> "Tibor Karaszi" wrote:
>> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This
>> behavior
>> change is documented in:
>> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "martin1" <martin1@.discussions.microsoft.com> wrote in message
>> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
>> > Hi, All,
>> >
>> > I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
>> > sql 2005 data, but the password is case seasitive. The sql 2000 is not case
>> > seasitive, anyone knows we can configure sql 2005 user password is not
>> > seasitive?
>> >
>> > Thanks for your time,
>> > Martin
>>|||Hi, Tibor Karaszi,
yuo mean sql server case seasitive can be changed by rebuidm.exe, this is
for sql 2000 or sql 2005?
Thanks
"Tibor Karaszi" wrote:
> 1: SQL Server 2000 and earlier: Whether a password is case sensitive or not is determined by the
> collation for the system databases (AFAIK), which was decided when you installed the SQL Server
> instances. To change this, you need to use rebuildm.exe which will scratch all the system databases,
> and should be performed unless you have good knowledge of the SQL Server architecture and can
> determine what such a rebuild will do.
> 2: This is an URL for the Books Online that comes with SQL Server 2005. It is installed when you
> install 2005, and you find an like in the SQL Server program group.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...
> > Hi, Tibor Karaszi,
> >
> > 1) if not in Sql 2005, do you know we can configute IIS web server is not
> > case seasitive?
> > 2) where to see
> > ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ? can
> > you tell how to go there.
> >
> > Thanks in advance,
> > Martin
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This
> >> behavior
> >> change is documented in:
> >> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> >> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
> >> > Hi, All,
> >> >
> >> > I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
> >> > sql 2005 data, but the password is case seasitive. The sql 2000 is not case
> >> > seasitive, anyone knows we can configure sql 2005 user password is not
> >> > seasitive?
> >> >
> >> > Thanks for your time,
> >> > Martin
> >>
> >>
>|||That only applies to 2000, logins are *always* case sensitive in 2005.
If you want to try this (2000): Make sure you test this on a test server first, as I'm not 100%
positive. But be aware that rebuildm does *a lot* of other things as well (it is pretty close to a
re-install). This is why I mentioned that you should be very familiar with what rebuildm does and
the consequences to running it, etc, before attempting this.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"martin1" <martin1@.discussions.microsoft.com> wrote in message
news:BF694D38-6032-4598-9CB6-4042F7D6BFC0@.microsoft.com...
> Hi, Tibor Karaszi,
> yuo mean sql server case seasitive can be changed by rebuidm.exe, this is
> for sql 2000 or sql 2005?
> Thanks
> "Tibor Karaszi" wrote:
>> 1: SQL Server 2000 and earlier: Whether a password is case sensitive or not is determined by the
>> collation for the system databases (AFAIK), which was decided when you installed the SQL Server
>> instances. To change this, you need to use rebuildm.exe which will scratch all the system
>> databases,
>> and should be performed unless you have good knowledge of the SQL Server architecture and can
>> determine what such a rebuild will do.
>> 2: This is an URL for the Books Online that comes with SQL Server 2005. It is installed when you
>> install 2005, and you find an like in the SQL Server program group.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "martin1" <martin1@.discussions.microsoft.com> wrote in message
>> news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...
>> > Hi, Tibor Karaszi,
>> >
>> > 1) if not in Sql 2005, do you know we can configute IIS web server is not
>> > case seasitive?
>> > 2) where to see
>> > ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ?
>> > can
>> > you tell how to go there.
>> >
>> > Thanks in advance,
>> > Martin
>> >
>> >
>> > "Tibor Karaszi" wrote:
>> >
>> >> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This
>> >> behavior
>> >> change is documented in:
>> >> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
>> >>
>> >> --
>> >> Tibor Karaszi, SQL Server MVP
>> >> http://www.karaszi.com/sqlserver/default.asp
>> >> http://www.solidqualitylearning.com/
>> >>
>> >>
>> >> "martin1" <martin1@.discussions.microsoft.com> wrote in message
>> >> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
>> >> > Hi, All,
>> >> >
>> >> > I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
>> >> > sql 2005 data, but the password is case seasitive. The sql 2000 is not case
>> >> > seasitive, anyone knows we can configure sql 2005 user password is not
>> >> > seasitive?
>> >> >
>> >> > Thanks for your time,
>> >> > Martin
>> >>
>> >>
>>|||Thank you so much!
Martin
"Tibor Karaszi" wrote:
> That only applies to 2000, logins are *always* case sensitive in 2005.
> If you want to try this (2000): Make sure you test this on a test server first, as I'm not 100%
> positive. But be aware that rebuildm does *a lot* of other things as well (it is pretty close to a
> re-install). This is why I mentioned that you should be very familiar with what rebuildm does and
> the consequences to running it, etc, before attempting this.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:BF694D38-6032-4598-9CB6-4042F7D6BFC0@.microsoft.com...
> > Hi, Tibor Karaszi,
> >
> > yuo mean sql server case seasitive can be changed by rebuidm.exe, this is
> > for sql 2000 or sql 2005?
> >
> > Thanks
> >
> > "Tibor Karaszi" wrote:
> >
> >> 1: SQL Server 2000 and earlier: Whether a password is case sensitive or not is determined by the
> >> collation for the system databases (AFAIK), which was decided when you installed the SQL Server
> >> instances. To change this, you need to use rebuildm.exe which will scratch all the system
> >> databases,
> >> and should be performed unless you have good knowledge of the SQL Server architecture and can
> >> determine what such a rebuild will do.
> >>
> >> 2: This is an URL for the Books Online that comes with SQL Server 2005. It is installed when you
> >> install 2005, and you find an like in the SQL Server program group.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> >> news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...
> >> > Hi, Tibor Karaszi,
> >> >
> >> > 1) if not in Sql 2005, do you know we can configute IIS web server is not
> >> > case seasitive?
> >> > 2) where to see
> >> > ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ?
> >> > can
> >> > you tell how to go there.
> >> >
> >> > Thanks in advance,
> >> > Martin
> >> >
> >> >
> >> > "Tibor Karaszi" wrote:
> >> >
> >> >> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This
> >> >> behavior
> >> >> change is documented in:
> >> >> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
> >> >>
> >> >> --
> >> >> Tibor Karaszi, SQL Server MVP
> >> >> http://www.karaszi.com/sqlserver/default.asp
> >> >> http://www.solidqualitylearning.com/
> >> >>
> >> >>
> >> >> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> >> >> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
> >> >> > Hi, All,
> >> >> >
> >> >> > I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
> >> >> > sql 2005 data, but the password is case seasitive. The sql 2000 is not case
> >> >> > seasitive, anyone knows we can configure sql 2005 user password is not
> >> >> > seasitive?
> >> >> >
> >> >> > Thanks for your time,
> >> >> > Martin
> >> >>
> >> >>
> >>
> >>
>
password case seasitive configuration
Hi, All,
I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
sql 2005 data, but the password is case seasitive. The sql 2000 is not case
seasitive, anyone knows we can configure sql 2005 user password is not
seasitive?
Thanks for your time,
MartinTo the best of my knowledge, you cannot change to case insensitive passwords
in 2005. This behavior
change is documented in:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-
cbee8013c995.htm
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"martin1" <martin1@.discussions.microsoft.com> wrote in message
news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
> Hi, All,
> I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
> sql 2005 data, but the password is case seasitive. The sql 2000 is not cas
e
> seasitive, anyone knows we can configure sql 2005 user password is not
> seasitive?
> Thanks for your time,
> Martin|||Hi, Tibor Karaszi,
1) if not in Sql 2005, do you know we can configute IIS web server is not
case seasitive?
2) where to see
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-
cbee8013c995.htm ? can you tell how to go there.
Thanks in advance,
Martin
"Tibor Karaszi" wrote:
> To the best of my knowledge, you cannot change to case insensitive passwor
ds in 2005. This behavior
> change is documented in:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b54
7-cbee8013c995.htm
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
>|||1: SQL Server 2000 and earlier: Whether a password is case sensitive or not
is determined by the
collation for the system databases (AFAIK), which was decided when you insta
lled the SQL Server
instances. To change this, you need to use rebuildm.exe which will scratch a
ll the system databases,
and should be performed unless you have good knowledge of the SQL Server arc
hitecture and can
determine what such a rebuild will do.
2: This is an URL for the Books Online that comes with SQL Server 2005. It i
s installed when you
install 2005, and you find an like in the SQL Server program group.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"martin1" <martin1@.discussions.microsoft.com> wrote in message
news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...[vbcol=seagreen]
> Hi, Tibor Karaszi,
> 1) if not in Sql 2005, do you know we can configute IIS web server is not
> case seasitive?
> 2) where to see
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b54
7-cbee8013c995.htm ? can
> you tell how to go there.
> Thanks in advance,
> Martin
>
> "Tibor Karaszi" wrote:
>|||Hi, Tibor Karaszi,
yuo mean sql server case seasitive can be changed by rebuidm.exe, this is
for sql 2000 or sql 2005?
Thanks
"Tibor Karaszi" wrote:
> 1: SQL Server 2000 and earlier: Whether a password is case sensitive or no
t is determined by the
> collation for the system databases (AFAIK), which was decided when you ins
talled the SQL Server
> instances. To change this, you need to use rebuildm.exe which will scratch
all the system databases,
> and should be performed unless you have good knowledge of the SQL Server a
rchitecture and can
> determine what such a rebuild will do.
> 2: This is an URL for the Books Online that comes with SQL Server 2005. It
is installed when you
> install 2005, and you find an like in the SQL Server program group.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...
>|||That only applies to 2000, logins are *always* case sensitive in 2005.
If you want to try this (2000): Make sure you test this on a test server fir
st, as I'm not 100%
positive. But be aware that rebuildm does *a lot* of other things as well (i
t is pretty close to a
re-install). This is why I mentioned that you should be very familiar with w
hat rebuildm does and
the consequences to running it, etc, before attempting this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"martin1" <martin1@.discussions.microsoft.com> wrote in message
news:BF694D38-6032-4598-9CB6-4042F7D6BFC0@.microsoft.com...[vbcol=seagreen]
> Hi, Tibor Karaszi,
> yuo mean sql server case seasitive can be changed by rebuidm.exe, this is
> for sql 2000 or sql 2005?
> Thanks
> "Tibor Karaszi" wrote:
>|||Thank you so much!
Martin
"Tibor Karaszi" wrote:
> That only applies to 2000, logins are *always* case sensitive in 2005.
> If you want to try this (2000): Make sure you test this on a test server f
irst, as I'm not 100%
> positive. But be aware that rebuildm does *a lot* of other things as well
(it is pretty close to a
> re-install). This is why I mentioned that you should be very familiar with
what rebuildm does and
> the consequences to running it, etc, before attempting this.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:BF694D38-6032-4598-9CB6-4042F7D6BFC0@.microsoft.com...
>
I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
sql 2005 data, but the password is case seasitive. The sql 2000 is not case
seasitive, anyone knows we can configure sql 2005 user password is not
seasitive?
Thanks for your time,
MartinTo the best of my knowledge, you cannot change to case insensitive passwords
in 2005. This behavior
change is documented in:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-
cbee8013c995.htm
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"martin1" <martin1@.discussions.microsoft.com> wrote in message
news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
> Hi, All,
> I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
> sql 2005 data, but the password is case seasitive. The sql 2000 is not cas
e
> seasitive, anyone knows we can configure sql 2005 user password is not
> seasitive?
> Thanks for your time,
> Martin|||Hi, Tibor Karaszi,
1) if not in Sql 2005, do you know we can configute IIS web server is not
case seasitive?
2) where to see
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-
cbee8013c995.htm ? can you tell how to go there.
Thanks in advance,
Martin
"Tibor Karaszi" wrote:
> To the best of my knowledge, you cannot change to case insensitive passwor
ds in 2005. This behavior
> change is documented in:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b54
7-cbee8013c995.htm
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
>|||1: SQL Server 2000 and earlier: Whether a password is case sensitive or not
is determined by the
collation for the system databases (AFAIK), which was decided when you insta
lled the SQL Server
instances. To change this, you need to use rebuildm.exe which will scratch a
ll the system databases,
and should be performed unless you have good knowledge of the SQL Server arc
hitecture and can
determine what such a rebuild will do.
2: This is an URL for the Books Online that comes with SQL Server 2005. It i
s installed when you
install 2005, and you find an like in the SQL Server program group.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"martin1" <martin1@.discussions.microsoft.com> wrote in message
news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...[vbcol=seagreen]
> Hi, Tibor Karaszi,
> 1) if not in Sql 2005, do you know we can configute IIS web server is not
> case seasitive?
> 2) where to see
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b54
7-cbee8013c995.htm ? can
> you tell how to go there.
> Thanks in advance,
> Martin
>
> "Tibor Karaszi" wrote:
>|||Hi, Tibor Karaszi,
yuo mean sql server case seasitive can be changed by rebuidm.exe, this is
for sql 2000 or sql 2005?
Thanks
"Tibor Karaszi" wrote:
> 1: SQL Server 2000 and earlier: Whether a password is case sensitive or no
t is determined by the
> collation for the system databases (AFAIK), which was decided when you ins
talled the SQL Server
> instances. To change this, you need to use rebuildm.exe which will scratch
all the system databases,
> and should be performed unless you have good knowledge of the SQL Server a
rchitecture and can
> determine what such a rebuild will do.
> 2: This is an URL for the Books Online that comes with SQL Server 2005. It
is installed when you
> install 2005, and you find an like in the SQL Server program group.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...
>|||That only applies to 2000, logins are *always* case sensitive in 2005.
If you want to try this (2000): Make sure you test this on a test server fir
st, as I'm not 100%
positive. But be aware that rebuildm does *a lot* of other things as well (i
t is pretty close to a
re-install). This is why I mentioned that you should be very familiar with w
hat rebuildm does and
the consequences to running it, etc, before attempting this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"martin1" <martin1@.discussions.microsoft.com> wrote in message
news:BF694D38-6032-4598-9CB6-4042F7D6BFC0@.microsoft.com...[vbcol=seagreen]
> Hi, Tibor Karaszi,
> yuo mean sql server case seasitive can be changed by rebuidm.exe, this is
> for sql 2000 or sql 2005?
> Thanks
> "Tibor Karaszi" wrote:
>|||Thank you so much!
Martin
"Tibor Karaszi" wrote:
> That only applies to 2000, logins are *always* case sensitive in 2005.
> If you want to try this (2000): Make sure you test this on a test server f
irst, as I'm not 100%
> positive. But be aware that rebuildm does *a lot* of other things as well
(it is pretty close to a
> re-install). This is why I mentioned that you should be very familiar with
what rebuildm does and
> the consequences to running it, etc, before attempting this.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:BF694D38-6032-4598-9CB6-4042F7D6BFC0@.microsoft.com...
>
password case seasitive configuration
Hi, All,
I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
sql 2005 data, but the password is case seasitive. The sql 2000 is not case
seasitive, anyone knows we can configure sql 2005 user password is not
seasitive?
Thanks for your time,
Martin
Hi, Tibor Karaszi,
1) if not in Sql 2005, do you know we can configute IIS web server is not
case seasitive?
2) where to see
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ? can you tell how to go there.
Thanks in advance,
Martin
"Tibor Karaszi" wrote:
> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This behavior
> change is documented in:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
>
|||Hi, Tibor Karaszi,
yuo mean sql server case seasitive can be changed by rebuidm.exe, this is
for sql 2000 or sql 2005?
Thanks
"Tibor Karaszi" wrote:
> 1: SQL Server 2000 and earlier: Whether a password is case sensitive or not is determined by the
> collation for the system databases (AFAIK), which was decided when you installed the SQL Server
> instances. To change this, you need to use rebuildm.exe which will scratch all the system databases,
> and should be performed unless you have good knowledge of the SQL Server architecture and can
> determine what such a rebuild will do.
> 2: This is an URL for the Books Online that comes with SQL Server 2005. It is installed when you
> install 2005, and you find an like in the SQL Server program group.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...
>
|||Thank you so much!
Martin
"Tibor Karaszi" wrote:
> That only applies to 2000, logins are *always* case sensitive in 2005.
> If you want to try this (2000): Make sure you test this on a test server first, as I'm not 100%
> positive. But be aware that rebuildm does *a lot* of other things as well (it is pretty close to a
> re-install). This is why I mentioned that you should be very familiar with what rebuildm does and
> the consequences to running it, etc, before attempting this.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:BF694D38-6032-4598-9CB6-4042F7D6BFC0@.microsoft.com...
>
I just upgrade sql 2000 to sql 2005, and try to run asp webpage to access
sql 2005 data, but the password is case seasitive. The sql 2000 is not case
seasitive, anyone knows we can configure sql 2005 user password is not
seasitive?
Thanks for your time,
Martin
Hi, Tibor Karaszi,
1) if not in Sql 2005, do you know we can configute IIS web server is not
case seasitive?
2) where to see
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm ? can you tell how to go there.
Thanks in advance,
Martin
"Tibor Karaszi" wrote:
> To the best of my knowledge, you cannot change to case insensitive passwords in 2005. This behavior
> change is documented in:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/65eaafa1-9e06-4264-b547-cbee8013c995.htm
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:6108FE0B-D229-4E56-9CC9-9483AA210FC6@.microsoft.com...
>
|||Hi, Tibor Karaszi,
yuo mean sql server case seasitive can be changed by rebuidm.exe, this is
for sql 2000 or sql 2005?
Thanks
"Tibor Karaszi" wrote:
> 1: SQL Server 2000 and earlier: Whether a password is case sensitive or not is determined by the
> collation for the system databases (AFAIK), which was decided when you installed the SQL Server
> instances. To change this, you need to use rebuildm.exe which will scratch all the system databases,
> and should be performed unless you have good knowledge of the SQL Server architecture and can
> determine what such a rebuild will do.
> 2: This is an URL for the Books Online that comes with SQL Server 2005. It is installed when you
> install 2005, and you find an like in the SQL Server program group.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:059E056C-0F3A-4DCE-AADA-9EDE468DAAE6@.microsoft.com...
>
|||Thank you so much!
Martin
"Tibor Karaszi" wrote:
> That only applies to 2000, logins are *always* case sensitive in 2005.
> If you want to try this (2000): Make sure you test this on a test server first, as I'm not 100%
> positive. But be aware that rebuildm does *a lot* of other things as well (it is pretty close to a
> re-install). This is why I mentioned that you should be very familiar with what rebuildm does and
> the consequences to running it, etc, before attempting this.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "martin1" <martin1@.discussions.microsoft.com> wrote in message
> news:BF694D38-6032-4598-9CB6-4042F7D6BFC0@.microsoft.com...
>
Passing table variable as input parameter to stored proc
I understand you cannot pass a table variable as input parameter to a stored
proc.
But what is the alternative in my case?
Current DB standards limit access of linked servers to the execution of
stored procs and functions, no cross server joins.
But I need to get data from the remote server that matches keys on imy local
server. The remote table is too large to bring over to the local server in
its entirety. In order to limit my result set from the remote server, I must
pass it the
keys of the records I want.
My issue is how to pass the keys.
For example, say I have customers and orders databases are on different
servers. From orders I want to get customer information for 200 customers.
Somehow I need to pass 200 custids to customers, execute the query there and
return 200 sets of customer data.
How do I call a proc on orders and pass 200 custids as a parameter?You can always query on a table of some other database on some other
server by specifying server name, db name, owner name and table name.
Something like this:
SELECT * FROM <Server Name>.<Database Name>.<Owner>.<Table>
If you have any other concern which is not covered here, please write.
I will surely try to help you.
Thanks|||Dave
Table-Valued UDFs --
USE Northwind
GO
IF object_id('dbo.get_cust_orders') IS NOT NULL
DROP FUNCTION dbo.cust_orders
GO
CREATE FUNCTION dbo.get_cust_orders
(
@.custid char(5)
)
RETURNS TABLE
AS
RETURN SELECT
*
FROM
Orders
WHERE
CustomerID = @.custid
GO
SELECT OrderID, OrderDate
FROM get_cust_orders('VINET') AS C
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:BFDF4510-EDA1-4098-BCCA-E2C80EAFFA73@.microsoft.com...
>I understand you cannot pass a table variable as input parameter to a
>stored
> proc.
> But what is the alternative in my case?
> Current DB standards limit access of linked servers to the execution of
> stored procs and functions, no cross server joins.
> But I need to get data from the remote server that matches keys on imy
> local
> server. The remote table is too large to bring over to the local server
> in
> its entirety. In order to limit my result set from the remote server, I
> must
> pass it the
> keys of the records I want.
> My issue is how to pass the keys.
> For example, say I have customers and orders databases are on different
> servers. From orders I want to get customer information for 200
> customers.
> Somehow I need to pass 200 custids to customers, execute the query there
> and
> return 200 sets of customer data.
> How do I call a proc on orders and pass 200 custids as a parameter?
>
proc.
But what is the alternative in my case?
Current DB standards limit access of linked servers to the execution of
stored procs and functions, no cross server joins.
But I need to get data from the remote server that matches keys on imy local
server. The remote table is too large to bring over to the local server in
its entirety. In order to limit my result set from the remote server, I must
pass it the
keys of the records I want.
My issue is how to pass the keys.
For example, say I have customers and orders databases are on different
servers. From orders I want to get customer information for 200 customers.
Somehow I need to pass 200 custids to customers, execute the query there and
return 200 sets of customer data.
How do I call a proc on orders and pass 200 custids as a parameter?You can always query on a table of some other database on some other
server by specifying server name, db name, owner name and table name.
Something like this:
SELECT * FROM <Server Name>.<Database Name>.<Owner>.<Table>
If you have any other concern which is not covered here, please write.
I will surely try to help you.
Thanks|||Dave
Table-Valued UDFs --
USE Northwind
GO
IF object_id('dbo.get_cust_orders') IS NOT NULL
DROP FUNCTION dbo.cust_orders
GO
CREATE FUNCTION dbo.get_cust_orders
(
@.custid char(5)
)
RETURNS TABLE
AS
RETURN SELECT
*
FROM
Orders
WHERE
CustomerID = @.custid
GO
SELECT OrderID, OrderDate
FROM get_cust_orders('VINET') AS C
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:BFDF4510-EDA1-4098-BCCA-E2C80EAFFA73@.microsoft.com...
>I understand you cannot pass a table variable as input parameter to a
>stored
> proc.
> But what is the alternative in my case?
> Current DB standards limit access of linked servers to the execution of
> stored procs and functions, no cross server joins.
> But I need to get data from the remote server that matches keys on imy
> local
> server. The remote table is too large to bring over to the local server
> in
> its entirety. In order to limit my result set from the remote server, I
> must
> pass it the
> keys of the records I want.
> My issue is how to pass the keys.
> For example, say I have customers and orders databases are on different
> servers. From orders I want to get customer information for 200
> customers.
> Somehow I need to pass 200 custids to customers, execute the query there
> and
> return 200 sets of customer data.
> How do I call a proc on orders and pass 200 custids as a parameter?
>
Subscribe to:
Posts (Atom)