I had a WSS 2.0 site (no custom parts) that I needed to upgrade AND migrate to another server. So I pretty much followed the advice on http://geekswithblogs.net/redwards/archive/2007/10/26/116365.aspx .
The above article is unclear about how the DB was transferred however, so had to wing it. Basically what I ended up doing was copying the .mdf and .ldf files of the WSS 2.0 content DB over to the Data folder of a SQL Express 2005 server --NOT the WSS 3.0 embedded DB (I tried that, but it gave me errors when I ran stsadm).
Note, after the DB was added and all set up in the Central Administration, I had to change the site collection administrator. The migrated site still had the OldServer\Administrator as the Primary site collection administrator. Other than that pretty seamless...
Providing Rest Clients Nearly as Bad as Publishing SOAP Contracts
-
Even still, many developers and architects have continued to emotionally
cling to the SOAP bad old days, wherein the contracts between a server and
a cli...
5 years ago