I currently have a WinXP system which has MSDE installed. I am replacing
that system with a new one and I want to install MSDE and then move a copy
of all my current DBs. I have MS Office 2003 and I plan to install MSDE from
those CDs. To move copies of the DBs I plan to Detach them at the old
system, copy the DB to the new system and attach it there (and attach it
back on the old system as well - just to be safe)
Is that a reasonable approach or is there a better way?
Wayne
hi Wayne,
Wayne Wengert wrote:
> I currently have a WinXP system which has MSDE installed. I am
> replacing that system with a new one and I want to install MSDE and
> then move a copy of all my current DBs. I have MS Office 2003 and I
> plan to install MSDE from those CDs. To move copies of the DBs I plan
> to Detach them at the old system, copy the DB to the new system and
> attach it there (and attach it back on the old system as well - just
> to be safe)
> Is that a reasonable approach or is there a better way?
> Wayne
it's a reasonable approach ... you can go on..
just a note... if you use SQL Server standard logins, please verify orphaned
user, that's to say users no longer in sync with their respective logins...
this sync is established on the sid column of database..sysusers and
master..syslogins, and where NULL is returned you have orhpaned users
problems.. so please check
http://msdn.microsoft.com/library/de...ca-cz_8qzy.asp
for sp_change_users_login system stored procedure synopsis and
http://www.sqlservercentral.com/colu...okenlogins.asp
Neil Boyle article for further info..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks. Will do!
Wayne
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3cdnj9F6l0itoU1@.individual.net...
> hi Wayne,
> Wayne Wengert wrote:
> it's a reasonable approach ... you can go on..
> just a note... if you use SQL Server standard logins, please verify
orphaned
> user, that's to say users no longer in sync with their respective
logins...
> this sync is established on the sid column of database..sysusers and
> master..syslogins, and where NULL is returned you have orhpaned users
> problems.. so please check
>
http://msdn.microsoft.com/library/de...ca-cz_8qzy.asp
> for sp_change_users_login system stored procedure synopsis and
> http://www.sqlservercentral.com/colu...okenlogins.asp
> Neil Boyle article for further info..
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
No comments:
Post a Comment