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:
>

Moving an Access Database to SQL Server.

Is there a way of taking an access database and create a replica of that
database as a sql Server database, but only doing it by code. Reason being I
am asking this is because we currently have clients that are running on an
access database using the access runtime and I am installing the Microsoft
Sql Server Desktop Engine (MSDE) and wish to transfer their existing access
database to the SQL Server Environment. I would like the user to do this
function through my program, and also make it easy for them to use.search on comp.databases.ms-access for this I'm sure you'll find what
you need.|||It is straightforward to build a DTS package that imports all MS Access
tables to SQL Server. One option is to open the package in the designer and
then Package.. Save As.. the package as a Visual Basic project which can be
compiled as an executable for distribution to the client.
http://msdn.microsoft.com/library/d...>
wiz_9e5g.asp
http://msdn.microsoft.com/library/d...br />
8jfp.asp
However, keep in mind that some queries designed for MS Access may not be
compatable with SQL Server.
http://www.microsoft.com/technet/pr...rt11/sqc18.mspx
"Db_Stuff" <DbStuff@.discussions.microsoft.com> wrote in message
news:A59D96E3-BCBE-44C0-97CA-E94D0A3AF435@.microsoft.com...
> Is there a way of taking an access database and create a replica of that
> database as a sql Server database, but only doing it by code. Reason being
> I
> am asking this is because we currently have clients that are running on an
> access database using the access runtime and I am installing the Microsoft
> Sql Server Desktop Engine (MSDE) and wish to transfer their existing
> access
> database to the SQL Server Environment. I would like the user to do this
> function through my program, and also make it easy for them to use.|||>> I am installing the Microsoft Sql Server Desktop Engine (MSDE)
I'm not sure if he has access to DTS, it's not part of MSDE.
And Access itself has upsizing functionality|||Creating the DTS package would require SQL Server developer edition or
higher, but it can be run against MSDE.
"Gerard" <g.doeswijk@.gmail.com> wrote in message
news:1134052256.228445.111720@.o13g2000cwo.googlegroups.com...
> I'm not sure if he has access to DTS, it's not part of MSDE.
> And Access itself has upsizing functionality
>|||The Access Upsizing Wizard accessible from the tools menu should transfer
Access data to SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"JT" <someone@.microsoft.com> wrote in message
news:Ox2FVuA$FHA.3392@.TK2MSFTNGP14.phx.gbl...
> Creating the DTS package would require SQL Server developer edition or
> higher, but it can be run against MSDE.
> "Gerard" <g.doeswijk@.gmail.com> wrote in message
> news:1134052256.228445.111720@.o13g2000cwo.googlegroups.com...
>|||Will the Upsizing Wizard translate (if needed) the SQL queries. It sounds
like perhaps the OP has an Access application (or at least an application
that has been using Access) and he wants to upsize the backend database to
SQL Server.
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:O9UKt2A$FHA.356@.TK2MSFTNGP12.phx.gbl...
> The Access Upsizing Wizard accessible from the tools menu should transfer
> Access data to SQL Server
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "JT" <someone@.microsoft.com> wrote in message
> news:Ox2FVuA$FHA.3392@.TK2MSFTNGP14.phx.gbl...
>|||No, the upsizing wizard just moves the data you may or may no have to change
queries depending on your application. In general, SQL Server is enough
different than Jet that some queries will have to be rewritten to get decent
performance.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"JT" <someone@.microsoft.com> wrote in message
news:O2dbCQB$FHA.2420@.TK2MSFTNGP12.phx.gbl...
> Will the Upsizing Wizard translate (if needed) the SQL queries. It sounds
> like perhaps the OP has an Access application (or at least an application
> that has been using Access) and he wants to upsize the backend database to
> SQL Server.
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:O9UKt2A$FHA.356@.TK2MSFTNGP12.phx.gbl...
>

Move log file without shutdown

I need to move a database's log file to a different disk. Can I do this without shutting down? It's pretty clear that I can create a second log file on the new disk but, what do I have to do to delete the old log file? The documentation warns that files must be empty to be deleted but I can't find any information on how to empty and disable a log file.

Will a BACKUP LOG make the log file empty enough to be deleted? How do I make sure that new transactions are all written to the new log file?

You can't move the primary log file whilst the db is online, i.e. the one you create with the database.

You could add another and then shrink the original and set the auto grow to off, but thats not ideal.

Why can't you take the DB offline for 5 minutes?

|||

Dang. I guess I'll have to take the database offline for 5 minutes. I was hoping to avoid that because even 5 minutes of downtime is going to take an hour of coordination, communication etc. This db is used during hospital admissions.