Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Migration from SQL 2000 to SQL 2005 expressMigration from SQL 2000 to SQL 2005 express
Previous
 
Next
New Post
7/6/2006 4:48 AM
 

Hi,

It's been many days that i'm struggling with this...

I can't solve out or even find info about how to migrate the database from a SQL 2000 on W2K3 server to a SQL 2005 express on W2K3. The IIS server is still the same (also hosting SQL 2005 express)

I thought it would be very easy:

- export of all data with the export data method

- changes in webconfig

<!-- Connection String for SQL Server 2005 Express -->

<add

name="SiteSqlServer"

connectionString="Data Source=BTPFINSWEB001\SQLExpress;database=dotnetnuke_intranet;uid=*****;pwd=*****;"

providerName="System.Data.SqlClient" />

 

But still get this error:

DotNetNuke Upgrade Error
The Assembly Version ( [ASSEMBLYVERSION] ) does not match the Database Version ( [DATABASEVERSION] )

ERROR: Could not connect to database.

The stored procedure 'dbo.GetPortalAliasByPortalID' doesn't exist

 

Thanks for any kind of help

 
New Post
7/6/2006 5:44 AM
 
It lookslike not all the objects are being created in the SQL 2005 server or the login your using in your connection string is orphaned.

A fool proof method of migrating is to create your DB login in the 2005 DB server. Detach the DB from the 2000 server and attach it in the 2005 server. Then run this on the SQL 2005 server do fix the orhaned login:

--Resolve an orphaned user

USE <your_db_name>;
GO
sp_change_users_login @Action='update_one', @UserNamePattern='<database_user>', @LoginName='<login_name>';
GO

--Alter User password

USE master
GO
sp_password @old=NULL, @new='password', @loginame='<login_name>';
GO

That's it. To varify that the DB has no ophaned users you can run this:

USE <your_db_name>
GO
sp_change_users_login @Action='Report';
GO




 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Migration from SQL 2000 to SQL 2005 expressMigration from SQL 2000 to SQL 2005 express


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out