Exporting MSDE database from one installation to another

I have two hard drives, one contains a previous installation of MSDE and a
non-bootable OS and there is a database on that installation that I need to
import to my new MSDE instance on the new hard drive. Is there an easy way
to do this?Hi,
Since OS is non bootable , there is no chance to detach or to do a backup
all databases. Only option is:-
1. Copy all .MDF and .LDF files to a new folder (safe location)
2. Install SQL server and same Service packs (as old) in the identical
folder (Same as old installation)
3. Stop the new MSDE
4. Copy the .MDF and .LDF files (took in step 1) to the same folders (Same
as old installation).
5. Start MSDE
Now login to query analyzer or enterprise manager and confirm all the
databases are online.
Thanks
Hari
MCDBA
"Kal525" <Kal525@.discussions.microsoft.com> wrote in message
news:81E57616-2B2F-4426-AD58-4CE39EAA78D1@.microsoft.com...
> I have two hard drives, one contains a previous installation of MSDE and a
> non-bootable OS and there is a database on that installation that I need
to
> import to my new MSDE instance on the new hard drive. Is there an easy
way
> to do this?

Exporting MSDE database from one installation to another

I have two hard drives, one contains a previous installation of MSDE and a
non-bootable OS and there is a database on that installation that I need to
import to my new MSDE instance on the new hard drive. Is there an easy way
to do this?
Hi,
Since OS is non bootable , there is no chance to detach or to do a backup
all databases. Only option is:-
1. Copy all .MDF and .LDF files to a new folder (safe location)
2. Install SQL server and same Service packs (as old) in the identical
folder (Same as old installation)
3. Stop the new MSDE
4. Copy the .MDF and .LDF files (took in step 1) to the same folders (Same
as old installation).
5. Start MSDE
Now login to query analyzer or enterprise manager and confirm all the
databases are online.
Thanks
Hari
MCDBA
"Kal525" <Kal525@.discussions.microsoft.com> wrote in message
news:81E57616-2B2F-4426-AD58-4CE39EAA78D1@.microsoft.com...
> I have two hard drives, one contains a previous installation of MSDE and a
> non-bootable OS and there is a database on that installation that I need
to
> import to my new MSDE instance on the new hard drive. Is there an easy
way
> to do this?
sql

Exporting MSDE database from one installation to another

I have two hard drives, one contains a previous installation of MSDE and a
non-bootable OS and there is a database on that installation that I need to
import to my new MSDE instance on the new hard drive. Is there an easy way
to do this?Hi,
Since OS is non bootable , there is no chance to detach or to do a backup
all databases. Only option is:-
1. Copy all .MDF and .LDF files to a new folder (safe location)
2. Install SQL server and same Service packs (as old) in the identical
folder (Same as old installation)
3. Stop the new MSDE
4. Copy the .MDF and .LDF files (took in step 1) to the same folders (Same
as old installation).
5. Start MSDE
Now login to query analyzer or enterprise manager and confirm all the
databases are online.
Thanks
Hari
MCDBA
"Kal525" <Kal525@.discussions.microsoft.com> wrote in message
news:81E57616-2B2F-4426-AD58-4CE39EAA78D1@.microsoft.com...
> I have two hard drives, one contains a previous installation of MSDE and a
> non-bootable OS and there is a database on that installation that I need
to
> import to my new MSDE instance on the new hard drive. Is there an easy
way
> to do this?

Export Stored Procedure SQL Script

We usually keep an "installation " table , when we save out stored
procedures they are ordered by the stated execution order. (customised
script)
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
___________________________________
"Alan" <alanpltseNOSPAM@.yahoo.com.au> wrote in message
news:eXOzROPmGHA.4164@.TK2MSFTNGP03.phx.gbl...
> I just use the 'Generate SQL Script' from EM to export stored procedure.
> How do I export the Stored Procedure SQL Script in to a file so in an
order
> so that they can be created successfully ?
> I got an error when execute the scripts:
> Cannot add rows to sysdepends for the current stored procedure because it
> depends on the missing object 'sp1'. The stored procedure will still be
> created.
> Cannot add rows to sysdepends for the current stored procedure because it
> depends on the missing object 'sp2'. The stored procedure will still be
> created.
> ...............
> ...............
> How do I get around that ?
>I just use the 'Generate SQL Script' from EM to export stored procedure.
How do I export the Stored Procedure SQL Script in to a file so in an order
so that they can be created successfully ?
I got an error when execute the scripts:
Cannot add rows to sysdepends for the current stored procedure because it
depends on the missing object 'sp1'. The stored procedure will still be
created.
Cannot add rows to sysdepends for the current stored procedure because it
depends on the missing object 'sp2'. The stored procedure will still be
created.
...............
...............
How do I get around that ?|||We usually keep an "installation " table , when we save out stored
procedures they are ordered by the stated execution order. (customised
script)
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
___________________________________
"Alan" <alanpltseNOSPAM@.yahoo.com.au> wrote in message
news:eXOzROPmGHA.4164@.TK2MSFTNGP03.phx.gbl...
> I just use the 'Generate SQL Script' from EM to export stored procedure.
> How do I export the Stored Procedure SQL Script in to a file so in an
order
> so that they can be created successfully ?
> I got an error when execute the scripts:
> Cannot add rows to sysdepends for the current stored procedure because it
> depends on the missing object 'sp1'. The stored procedure will still be
> created.
> Cannot add rows to sysdepends for the current stored procedure because it
> depends on the missing object 'sp2'. The stored procedure will still be
> created.
> ...............
> ...............
> How do I get around that ?
>

Export SQLServer Agent Job?

We have a new SQLServer 2000 installation and are moving over databases from
a SQLServer 7 installation. How do we bring over the SQLServer Agent jobs?
Thanks in advance,
MikeYou can script them... right click, All Tasks >, generate SQL script
"Mike Lopez" <mikelpez@.optonline.net> wrote in message
news:Ort9RfQYDHA.2284@.TK2MSFTNGP12.phx.gbl...
> We have a new SQLServer 2000 installation and are moving over databases
from
> a SQLServer 7 installation. How do we bring over the SQLServer Agent jobs?
> Thanks in advance,
> Mike
>|||> Once the script is generated what then? Copy it to the new SQL Server 2000
> server and execute it in Query Analyzer?
You might have to adjust server names etc., if they are included in the
script output. But generally, yes, that's the idea. I usually save such
scripts as <jobname>.job.sql files... this way they get the right icon in
Windows explorer, are recognized by Visual Studio / QA, but they also are
clearly marked as a JOB (whereas with the JOB extension, it gets a red x
like a windows scheduled task that doesn't work, at least in W2K3).
And as Chinna points out, you could also use the DTS task "transfer jobs"...