Moving an MSDE app to SQL Express

I have an MSDE application that I am trying to Move to SQLExpress without to
o
many changes. The application uses SQL Scripts to create logins, called
sp_addlogin. One of the logins that is created is a user with view only
rights to non_sensitive security parts of the schema. This user is created
with a null password.
With SQL Express sp_addlogin fails because the password does not meet the
complexity requirements. To assign a password to this login, the app would
need to be altered in ways that I would rather avoid at the moment. While I
understand that it is the long term correct way to go, is there a way that I
can get the scripts to both work on MSDE and SQLExpress with a null password
.
Or is my best bet to determine the version of the server and use CREATE LOGI
N
with CHECK_POLICY set to off
Thank You
LeslieIf you are willing to do the check and use CREATE LOGIN that would work, but
you are asking for trouble if you use a blank password.
--
Rob Walters
Program Manager - SQL Server
"Leslie" wrote:

> I have an MSDE application that I am trying to Move to SQLExpress without
too
> many changes. The application uses SQL Scripts to create logins, called
> sp_addlogin. One of the logins that is created is a user with view only
> rights to non_sensitive security parts of the schema. This user is created
> with a null password.
> With SQL Express sp_addlogin fails because the password does not meet the
> complexity requirements. To assign a password to this login, the app would
> need to be altered in ways that I would rather avoid at the moment. While
I
> understand that it is the long term correct way to go, is there a way that
I
> can get the scripts to both work on MSDE and SQLExpress with a null passwo
rd.
> Or is my best bet to determine the version of the server and use CREATE LO
GIN
> with CHECK_POLICY set to off
> Thank You
> Leslie|||Thank You.
I know it is asking for trouble. Unfortunatly the app was not written by me
and I don't have the ok from above to make the needed changes
Thanks again
-Leslie
"Rob Walters [MSFT]" wrote:
[vbcol=seagreen]
> If you are willing to do the check and use CREATE LOGIN that would work, b
ut
> you are asking for trouble if you use a blank password.
> --
> Rob Walters
> Program Manager - SQL Server
>
> "Leslie" wrote:
>

Moved database to new server...before creating logins

I feel like an idiot for this.
We are moving our SQL Server database (2000 Standard) to a new server
(also 2000 standard--don't worry, we've got a separate license for it).
What I did was backup the database on the old server and restore it to
the new server for testing our software application.
Only problem is, I didn't create the users beforehand, so now I can't
log into the new server with the login. It says I can't access my
default database.
WIthout dropping the database, is there a way I can fix this? It would
be easy enough to drop and re-restore the database, but if there is a
shorter way that would also work just as well, please enlighten me.Sure there are several articles here that cover this and more. But at the
least you can just create a new Login and then use sp_change_users_login to
map the user to the login.
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://www.databasejournal.com/feat...cle.php/3379901 Moving
system DB's
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scr...sp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
Andrew J. Kelly SQL MVP
"Brent White" <bwhite@.badgersportswear.com> wrote in message
news:1131724756.657385.127960@.f14g2000cwb.googlegroups.com...
>I feel like an idiot for this.
> We are moving our SQL Server database (2000 Standard) to a new server
> (also 2000 standard--don't worry, we've got a separate license for it).
> What I did was backup the database on the old server and restore it to
> the new server for testing our software application.
> Only problem is, I didn't create the users beforehand, so now I can't
> log into the new server with the login. It says I can't access my
> default database.
> WIthout dropping the database, is there a way I can fix this? It would
> be easy enough to drop and re-restore the database, but if there is a
> shorter way that would also work just as well, please enlighten me.
>|||Hi,
i found a good article by Mr. Vyas ,a very famous SQL Professional :
http://vyaskn.tripod.com/moving_sql_server.htm
Regards
--
Andy Davis
Activecrypt Team
---
SQL Server Encryption Software
http://www.activecrypt.com
"Brent White" wrote:

> I feel like an idiot for this.
> We are moving our SQL Server database (2000 Standard) to a new server
> (also 2000 standard--don't worry, we've got a separate license for it).
> What I did was backup the database on the old server and restore it to
> the new server for testing our software application.
> Only problem is, I didn't create the users beforehand, so now I can't
> log into the new server with the login. It says I can't access my
> default database.
> WIthout dropping the database, is there a way I can fix this? It would
> be easy enough to drop and re-restore the database, but if there is a
> shorter way that would also work just as well, please enlighten me.
>

Move SQL 7.0 to SQL 7.0

Hi,
moving all databases, users, logins DTS-jobs and so on from Server A to
(new) Server B.
What is the most efficient way of doing this? One example I have seen is to
copy all data and transaction-files for all databases.
Another way could be to perform Backup on Server A, and restore on Server B
(including msdb, master and so on) .
Any suggestions? Is there a way to make it simple ?
/BJI have not tryed it but try it yourself.
Install SQL Server on target machine in same path (and Service Packs).
Stop it.
Copy the SQL Server directory from source directory to target directory.
Copy all databases from source to destination keeping same location. If
databases need to be moved - you can detach it (from all tasks), move files
and attach them again.
Restart. Have fun
HTH
Bojidar Alexandrov|||I have also seen the "Server Upgrade Wizard".
Can this one be used for moving SQL7 to SQL7?
/BJ
"Bojidar Alexandrov" <bojo_do_not_spam@.kodar.net> wrote in message
news:ukHpDi1BEHA.464@.TK2MSFTNGP11.phx.gbl...
> I have not tryed it but try it yourself.
> Install SQL Server on target machine in same path (and Service Packs).
> Stop it.
> Copy the SQL Server directory from source directory to target directory.
> Copy all databases from source to destination keeping same location. If
> databases need to be moved - you can detach it (from all tasks), move
files
> and attach them again.
> Restart. Have fun
> HTH
> Bojidar Alexandrov
>|||> I have also seen the "Server Upgrade Wizard".
> Can this one be used for moving SQL7 to SQL7?
>
no|||OK,
you said that you have not tried this way, but what should your way be to
make it?
/BJ
"Bojidar Alexandrov" <bojo_do_not_spam@.kodar.net> wrote in message
news:OFpoAB2BEHA.2404@.TK2MSFTNGP11.phx.gbl...
> no
>|||As far as I know SQL Server this must works.
Try it on test machine and see for yourself - I personally do not have time
now|||here a article
http://www.databasejournal.com/feat...cle.php/1479841

Move logins with passwords

Hello!
I will reinstall my server who has SQL server 2000, containing a few
databases with logins.
Which is the easiest way to store these on disk and when I have reinstalled
my server, add these to SQL again, hopefully containing passwords as well.
Regards Magnushttp://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scr...sp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
Andrew J. Kelly
SQL Server MVP
"MB" <magnus.blomberg@.skanska.se> wrote in message
news:%23Qq4wnw9DHA.2404@.TK2MSFTNGP12.phx.gbl...
> Hello!
> I will reinstall my server who has SQL server 2000, containing a few
> databases with logins.
> Which is the easiest way to store these on disk and when I have
reinstalled
> my server, add these to SQL again, hopefully containing passwords as well.
> Regards Magnus
>|||Thank you. It helped
Regards Magnus
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OtBdL4w9DHA.1636@.TK2MSFTNGP12.phx.gbl...
> http://www.support.microsoft.com/?id=314546 Moving DB's between
Servers
> http://www.support.microsoft.com/?id=224071 Moving SQL Server
Databases
> to a New Location with Detach/Attach
> http://support.microsoft.com/?id=221465 Using WITH MOVE in a
> Restore
> http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
> Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after
a
> Restore
> http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
> users
> http://www.support.microsoft.com/?id=168001 User Logon and/or
Permission
> Errors After Restoring Dump
> http://www.support.microsoft.com/?id=240872 How to Resolve Permission
> Issues When a Database Is Moved Between SQL Servers
> http://www.sqlservercentral.com/scr...sp?scriptid=599
> Restoring a .mdf
> http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
> for SQL Server
>
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "MB" <magnus.blomberg@.skanska.se> wrote in message
> news:%23Qq4wnw9DHA.2404@.TK2MSFTNGP12.phx.gbl...
> reinstalled
well.
>

move logins from a sql 2000 server to a sql 2005 server

Hi guys,
I have tried to use the sp_help_revlogin script to move logins from a sql 2000 server to a sql 2005 server. It works for users that have a password. But if the password is blank it will fail. Is there a work around for this since I can't change the users passwords?
I have also tried SSIS package but that too doesn't work because of the same reason.

Can anyone help...

Users MUST have a password in SQL 2005. You will need to change the logins to have a password.