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

Can Create default instance with April CTP

First, it was a nightmare to get it installed. Multiple installs,uninstalls, deleted (really renamed) directories, and cleaned registries.

It gets an error that the connection was refused. It works fine for a named instance.

Since all of the MSSQLServer registry entries are new, I don't think it is there. And all are done with the service Local Account. So I think the problem must be in the TCP/IP configuration referring to an old installation.

What is the problem? Is there a reference to all of these registry entries.

Thanks,

DavidIt's very difficult to provide you an answer given the information you provided. Are you trying to access the instance remotely or locally? By default, TCP is off. To turn on remote connectivity you can use either SQL Configuration Manager or SQL Server Surface Area Configuration Manager.

Dan

"This posting is provided "AS IS" with no warranties, and confers no rights"|||This occurs during the installation, so it is before the utilities are available. What communications method does the setup program use that can be refused. It is only refused for the default instance.|||Are you saying this works if you install a named instance? That's strange. Can you grab the log files from: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\files\*.log. You can zip the files before attaching them.

Thanks,
Dan|||Hi David

Probably setup is finding an default instance in the machine. I suggest that you uninstall previous build using the command line:

Start /wait D:\SQLDEV_CTP4\setup.exe /qb REMOVE=ALL
Start /wait msiexec /qb /X D:\SQLDEV_CTP4\Setup\sqlncli.msi
Start /wait D:\SQLDEV_CTP4\redist\2.0\dotnetfx.exe /q:a /c:"install /qu"

where D:\SQLDEV_CTP4 is the way for which you it extracted the of setup files.

Another option is to use Build Uninstall Wizard (\Setup Tools\Build Uninstall Wizard),but still I think that command line is more efficient to remove one previous build.
regards
Nilton Pinheiro

|||Sorry to say, I've got this exact same situation, and the above doesn't fix the problem.

Can Create default instance with April CTP

First, it was a nightmare to get it installed. Multiple installs,uninstalls, deleted (really renamed) directories, and cleaned registries.

It gets an error that the connection was refused. It works fine for a named instance.

Since all of the MSSQLServer registry entries are new, I don't think it is there. And all are done with the service Local Account. So I think the problem must be in the TCP/IP configuration referring to an old installation.

What is the problem? Is there a reference to all of these registry entries.

Thanks,

DavidIt's very difficult to provide you an answer given the information you provided. Are you trying to access the instance remotely or locally? By default, TCP is off. To turn on remote connectivity you can use either SQL Configuration Manager or SQL Server Surface Area Configuration Manager.

Dan

"This posting is provided "AS IS" with no warranties, and confers no rights"|||This occurs during the installation, so it is before the utilities are available. What communications method does the setup program use that can be refused. It is only refused for the default instance.|||Are you saying this works if you install a named instance? That's strange. Can you grab the log files from: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\files\*.log. You can zip the files before attaching them.

Thanks,
Dan|||Hi David

Probably setup is finding an default instance in the machine. I suggest that you uninstall previous build using the command line:

Start /wait D:\SQLDEV_CTP4\setup.exe /qb REMOVE=ALL
Start /wait msiexec /qb /X D:\SQLDEV_CTP4\Setup\sqlncli.msi
Start /wait D:\SQLDEV_CTP4\redist\2.0\dotnetfx.exe /q:a /c:"install /qu"

where D:\SQLDEV_CTP4 is the way for which you it extracted the of setup files.

Another option is to use Build Uninstall Wizard (\Setup Tools\Build Uninstall Wizard),but still I think that command line is more efficient to remove one previous build.
regards
Nilton Pinheiro

|||Sorry to say, I've got this exact same situation, and the above doesn't fix the problem.