Re: "Best Practices" way to distribute MSDE
From: Ian Boyd (admin_at_SWIFTPA.NET)
Date: 07/09/04
- Next message: Sébastien Delestre: "Re: Error install MSDE without message in log file"
- Previous message: Liddle Feesh: "MSDE Merge Module Installer Error (.NET)"
- In reply to: Andrea Montanari: "Re: "Best Practices" way to distribute MSDE"
- Next in thread: Andrea Montanari: "Re: "Best Practices" way to distribute MSDE"
- Reply: Andrea Montanari: "Re: "Best Practices" way to distribute MSDE"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 8 Jul 2004 22:30:54 -0400
Now is there any Microsoft document that describes this typical situation of
a client's computer was re-installed, and they need their data back...
What is the best practice to do this?
Ways to put a database into a server:
Attach my empty db
Restore my empty db
Run scripts to create my empty db
Restore a users's selected backup.
Attach a users db from a previous install.
Is there a concensus on an interface, API, and routines to perform these
things are automatically as possible?
Remember, if i'm supposed to be using MSDE now instead of Jet: Jet was very
easy for the client to backup and restore. They copied the file when they
wanted a backup, and they put it into the folder when they wanted to
restore.
What is the MSDE equivalent procedures to accomplish the same task as
seamlessly for the end user without any vendor intervention or hand-holding?
What are the "Best Practices" way to distribute MSDE?
"Andrea Montanari" <andrea.sqlDMO@virgilio.it> wrote in message
news:2l3qjaF8auodU1@uni-berlin.de...
> hi Ian,
> "Ian Boyd" <admin@SWIFTPA.NET> ha scritto nel messaggio
> news:%23fiy0DIZEHA.2516@TK2MSFTNGP10.phx.gbl...
> > How do you determine if an SQL Server is already installed?
>
> you can (locally) check the registry, instantiate SQL-DMO (which only
tells
> if SQL-DMO is locally present) and try a connection to the server... this
> can be done via Ado/Ado.Net too...
>
> > If so, how do you detect if your database is already installed?
>
> query the database catalogue for it's name... SQL-DMO/Ado/Ado.Net
>
> > How do you detect if you login is already created?
>
> if you can't connect with that login, it's not there... or SQL-DMO or
> sp_helplogins 'login2test' via Ado/Ado.Net
>
> > If you login is not already created, but your database is, how do you
> relink
> > them?
>
> strange situation, isn't it? =;-D
> eventually, just re-add your login and grant db access, as long as all
> object privileges... SQL-DMO/Ado/Ado.Net
>
> > If you login is already there, but the database isn't how do you handle
> it?
>
> you just create the database... and then go on granting db access and
object
> privileges... SQL-DMO/Ado/Ado.Net
>
> just use traditional common sense =;-)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
> DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> --------- remove DMO to reply
>
- Next message: Sébastien Delestre: "Re: Error install MSDE without message in log file"
- Previous message: Liddle Feesh: "MSDE Merge Module Installer Error (.NET)"
- In reply to: Andrea Montanari: "Re: "Best Practices" way to distribute MSDE"
- Next in thread: Andrea Montanari: "Re: "Best Practices" way to distribute MSDE"
- Reply: Andrea Montanari: "Re: "Best Practices" way to distribute MSDE"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
