Re: Password's case sensitivity
From: sam (sam_at_discussions.microsoft.com)
Date: 01/26/05
- Next message: JJA: "User already exists in the current database but without LOGIN"
- Previous message: Dan Guzman: "Re: Password's case sensitivity"
- In reply to: Dan Guzman: "Re: Password's case sensitivity"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 26 Jan 2005 05:43:12 -0800
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:
> > 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...
> >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
> >> 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...
> >> > 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:
> >> >
> >> >> 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...
> >> >> > 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
> >> >> >> 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
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>
- Next message: JJA: "User already exists in the current database but without LOGIN"
- Previous message: Dan Guzman: "Re: Password's case sensitivity"
- In reply to: Dan Guzman: "Re: Password's case sensitivity"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
