Showing posts with label password. Show all posts
Showing posts with label password. Show all posts

Tuesday, March 20, 2012

Can I change a SQL Server Everywhere database's password?

Hi, I'm using the SQL Server Everywhere CTP on the desktop and haven't used SQL Server Mobile in the past.

I'm having some difficulty determining whether it's possible to change a SQL Server Everywhere database's password. Obviously authentication on a file-based SQL Server Everywhere database differs from that of server-based SQL Server database. Is it possible to change a SQL Server Everywhere database's password?

That said, I feel like I've made a decent search of the to change a SQL Server Everywhere books online. If it's not possible to change the password in place (i.e., without copying all data to a new file with a different password), please count this as a vote to add that functionality. Making a database password "permanent" lessens its effectiveness. Thanks,

Curt

Have you tried compacting the database? This was the way to go with SQL CE 2.0 - the compaction mechanism would create a new database with all the original's data and structure but then you had a chance to specify a new password.|||

Thanks, Jo?o.

Clearly I should have been looking under "Compact." :) I suppose if the password is used as an encyption key and setting a password implies using encryption then it was probably expedient to rewrite the password (and encrypted data) this way.

In the Compact docs:

You use the Compact method (the CompactDatabase method in native programming) to reclaim space in the database file. You can also use it to change database settings such as password and locale ID (LCID).

And in the CompactDatabase docs:

The CompactDatabase method reclaims wasted space in the local SQL Server 2005 Everywhere Edition (SQL Server Everywhere) database. This method can also be used to change the collating order, encryption, and password settings of the database.

|||

You can PASSWORD protect the database with out encrypting too. Set Password=xyz and Encrypt=false in connection string.

Thanks,

Laxmi Narsimha Rao ORUGANTI, SQL Server Everywhere

Can I change a SQL Server Everywhere database's password?

Hi, I'm using the SQL Server Everywhere CTP on the desktop and haven't used SQL Server Mobile in the past.

I'm having some difficulty determining whether it's possible to change a SQL Server Everywhere database's password. Obviously authentication on a file-based SQL Server Everywhere database differs from that of server-based SQL Server database. Is it possible to change a SQL Server Everywhere database's password?

That said, I feel like I've made a decent search of the to change a SQL Server Everywhere books online. If it's not possible to change the password in place (i.e., without copying all data to a new file with a different password), please count this as a vote to add that functionality. Making a database password "permanent" lessens its effectiveness. Thanks,

Curt

Have you tried compacting the database? This was the way to go with SQL CE 2.0 - the compaction mechanism would create a new database with all the original's data and structure but then you had a chance to specify a new password.|||

Thanks, Jo?o.

Clearly I should have been looking under "Compact." :) I suppose if the password is used as an encyption key and setting a password implies using encryption then it was probably expedient to rewrite the password (and encrypted data) this way.

In the Compact docs:

You use the Compact method (the CompactDatabase method in native programming) to reclaim space in the database file. You can also use it to change database settings such as password and locale ID (LCID).

And in the CompactDatabase docs:

The CompactDatabase method reclaims wasted space in the local SQL Server 2005 Everywhere Edition (SQL Server Everywhere) database. This method can also be used to change the collating order, encryption, and password settings of the database.

|||

You can PASSWORD protect the database with out encrypting too. Set Password=xyz and Encrypt=false in connection string.

Thanks,

Laxmi Narsimha Rao ORUGANTI, SQL Server Everywhere

Thursday, February 16, 2012

Can a Login/Password be validated against a Domain login/passord using a prompt dialog

I have an application database on SQL Server 2K and we've got an NT domain.
I want the users to type in their login and password, but I'd like to
validate that password against the windows NT Domain. Can this be done?
Jared HoffmanHi
This sounds like something that will not be permitted as you could then save
the users account details
You can use integrated security but you don't need a login box, unless you
want a secondary method of verification that you maintain.
John
"Jared Hoffman" <hoffmanj@.kenyon.edu.NO_SPAM> wrote in message
news:edQWKBfDEHA.3804@.TK2MSFTNGP09.phx.gbl...
> I have an application database on SQL Server 2K and we've got an NT
domain.
> I want the users to type in their login and password, but I'd like to
> validate that password against the windows NT Domain. Can this be done?
>
> Jared Hoffman
>|||If the users login to their domain, then they can simply use their nt
credentials to connect.
Change the SQL Server to use Windows Authentication. And change your
application connection string
to make Trusted Connections.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||My application will be used on computers that may or may not be joined to
the domain so I can't rely on Windows Authentication. I'd like to be able to
authenticate users in such a way I don't have to store another set of user
passwords.
Thanks,
Jared Hoffman
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:pd5X%23SfDEHA.3608@.cpmsftngxa06.phx.gbl...
> If the users login to their domain, then they can simply use their nt
> credentials to connect.
> Change the SQL Server to use Windows Authentication. And change your
> application connection string
> to make Trusted Connections.
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||previous post:
"My application will be used on computers that may or may not be joined to
the domain so I can't rely on Windows Authentication. I'd like to be able to
authenticate users in such a way I don't have to store another set of user
passwords.
"
Couple of options:
1. Standard SQL Security
2. Application roles
3. Trusted Security using duplicate nt username and passwords
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.