Since you don't want to update the 1000 MSDE systems, there are very few
options that don't involve reengineering or replacing the MSDE
systems--except for one. Install a MSDE instance on the server with 2005.
Setup a Merge Replication Publication on the host 2005 server. Setup a
Subscription to the data that you wish to propagate to the 1000 clients with
the host server (the Publisher). Once the replication is synchronized,
backup the MSDE database and distribute it to the 1000 clients.
Of course, there are far more reasonable ways to do this, but (again) all
require changes on the clients.
hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com www.betav.com/blog/billva Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit
www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------
"Karsten Lundsgaard" <Karsten Lundsgaard@discussions.microsoft.com> wrote in
message news:4E62CB04-022D-4415-B094-D4D9833966E2@microsoft.com...
[quoted text, click to view] > Hi, we have an application, that runs on 1000 PC's in different part of
> the
> world, and we are using MSDE to contain Configurations data.
> We are refreshing the data, by restoring a backup, made on our main
> server.
>
> We would like to upgrade the main server from MSSQL2000 to MSSQL2005.
> But there is one problem, we cannot restore a SQL2005-Backup, because it
> is
> in the 611-format.
>
> Is there some tool that can convert the backup-file from the 611-format to
> 539-format?
> Or is there some other way of solving this problem?
>
> I know that we can import the data on another server running MSSQL2000 and
> make a Backup. But we don't like this solution.:-(
>
> I hope someone can help us.
>
> Karsten Lundsgaard
Come back here (or give me a call) when you're ready to rethink this
approach. There are any number of inexpensive and easy-to-deploy solutions
that can leverage more recent technology--but they would involve changes on
the clients. For one thing, you might want to consider a "One-touch"
deployment strategy which can help deploy changes to the client applications
far easier.
hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com www.betav.com/blog/billva Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit
www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
-----------------------------------------------------------------------------------------------------------------------
"Karsten Lundsgaard" <KarstenLundsgaard@discussions.microsoft.com> wrote in
message news:BD46D977-CC83-4EB8-93BB-DD9DD981FD8E@microsoft.com...
[quoted text, click to view] > Thanks Bill.
>
> I think we will use your solution.
> We were hoping to find some 3th-party tool, that could help us.
>
> Karsten
Don't see what you're looking for? Try a search.
