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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DotNetNuke.Data.SqlDataProvider QuestionDotNetNuke.Data.SqlDataProvider Question
Previous
 
Next
New Post
10/4/2009 5:01 PM
 

 Hello,

I have a couple questions about the 'DotNetNuke.Data.SqlDataProvider' file that resides down Providers\DataProviders\SqlDataProvider.

1) What is it's purpose?  I understand the purpose of the other *.SqlDataProvider files because they relate to upgrade SQL scripts for a given DNN version.

The reason I ask the above question is that I had an upgrade from a 4.8.4 version to 5.01.02 that I thought I was running against a test copy database but ended up accidentally using a web.config that pointed to my live DB.  Ouch!  Then found out the backups for the live DB were bad.  Double OUCH!

Anyways, the 4.8.4 -> 5.01.02 didn't go well and I now cannot get to the "Module Definitions", "Skins" etc.  

I noticed after looking over the DB for a clean install of the latest version of DNN that a handful of DesktopModule, ModuleDef, TabModules, Modules table entries don't exist that would have to do with the items I see that are missing.  I see that in the "DotNetNuke.Data.SqlDataProvider" file there are 'insert into' scripts that load these specific tables with the information I need.  The problem is that I see the 'DotNetNuke.Data.SqlDataProvider" has hard coded identity ids that when I look at my corresponding tables are already taken.  For instance the DesktopModules 'insert into' part of script has this:

INSERT INTO {databaseOwner}[{objectQualifier}DesktopModules] ([DesktopModuleID], [FriendlyName], [Description], [Version], [IsPremium], [IsAdmin], [BusinessControllerClass], [FolderName], [ModuleName], [SupportedFeatures], [CompatibleVersions], [Dependencies], [Permissions], [PackageID]) VALUES (52, N'Extensions', N'Extensions.', N'01.00.00', 0, 1, NULL, N'Admin/Extensions', N'Extensions', 0, NULL, NULL, NULL, 52) 

The DesktopModuleID of 52 is already taken by another entry in my DB.  Can I tailor the sections of the DotNetNuke.Data.SqlDataProvider script that I want and change the identities to values other than those specified without causing some issue down the road where upgrades would be concerned with identity values that need to be the same as those specified in 'DotNetNuke.Data.SqlDataProvider'?  I know I'd have to also touch up the related table rows that are related to the rows I'd like to insert if I was able to go this route.

Thank you for your time on reading this and I look forward to your input!

Bill

 

 

 
New Post
10/5/2009 4:15 AM
 

Bill,

DotNetNuke.Data.SqlDataProvider script contains initial data to set up your portal. it is not re-runnable and assumes to run against a blank database using fixed id values. you may use it as a template to complete your upgraded portal, which will for sure contain a number of records in various metadata tables (moduleDefinitions etc).

 


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DotNetNuke.Data.SqlDataProvider QuestionDotNetNuke.Data.SqlDataProvider Question


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