By jbonnie on
Monday, July 17, 2006 3:00:23 AM
Migrating databases between production and development machines can be a challenge at times.I just ran into another complication for user accounts.When migrating databases, you probably are migrating the database and security information contained in it. You may not have the same users defined at the top level database level.If you simply try to create database users with the same names, you will run into problems. The new top level users will not have the same internal ID as the user defined in the moved database.Microsoft has a KB article on this, that shows how to migrate the database users along with the databases, the article for SQL 2005 is at How to transfer the logins and the passwords between instances of SQL Server 2005The KISS method for smaller development shops, is to just use different login names.After migrating the database, simply add a username to the moved database that already exists on the machine and you will...
Read More »
|
By jbonnie on
Wednesday, July 12, 2006 5:37:50 AM
I am using the brute force method of chaning the eventlog tables collation to the database default.
1) open the database with sql server management studio
2) expand, drilldown to the columns for the table in question
3) right click modify the columns that are are characters
4) go to extended properties and ensure the collation is set to database_default
This could be done with a T_SQL script, but brute force works for now...
Here is a screen print for the modify screen.
- Jim
|
By jbonnie on
Tuesday, July 11, 2006 1:59:50 PM
I am having trouble finding the download to the sample project for the DNN ClientAPI.
There are a lot of cool things with client callbacks and passing variables demo'ed.
I am logged into dotnetnuke and my screen appears as below.
Where should I look for the sample download project ??
Thanks for any help on finding it!!
|
By jbonnie on
Saturday, July 01, 2006 4:56:23 AM
Guess what happened on the way back from the simple transfer procedure from my ISP to my local development box. You guessed it, some new features added to DNN (or our modules) are causing some SQL Server Collation settings at the column level, which caused a conflict when moving the DB to another SQL host.I got the following error when calling up the DNN Log viewer,Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AI" in the equal to operation.I found these scripts that can help get things working again.This first script will show you the Collation settings for your DB, Server, and TempDB.Modify the DNNDB as appropiate.
SELECT
DATABASEPROPERTYEX( 'DNNDB' , 'Collation' ) AS DotNetNukeDB_Collation,
DATABASEPROPERTYEX( 'tempdb' , 'Collation' ) AS TempDB_Collation,
SERVERPROPERTY( 'Collation' ) AS Server_Default_CollationIf these are different then you can have a problem.This problem manifested after porting the production system locally...
Read More »
|
By jbonnie on
Friday, June 30, 2006 9:09:06 PM
This is a quick overview of how Virtualearth can be integrated into Dotnetnuke
Read More »
|
By jbonnie on
Friday, June 30, 2006 1:33:13 AM
The Virtual Earth module stopped working when Microsoft removed support for version2.
I have created a new DNN module to support VE3 and it is on the site.
The bird's eye view and control panel are pretty sweet. A number of module enhancements are required before release
Read More »
|
By jbonnie on
Wednesday, June 28, 2006 8:27:50 PM
The DNN 4.3.1 Patch set is out - Installed cleanly, fixes cacheing for the documents module, but still an issue with filtering by column (there is a work around).
Read More »
|
By jbonnie on
Thursday, June 15, 2006 5:17:39 AM
I installed DNN 4.03 on a dev box and was excited to see the new Documents module.
But there appears to be some bugs!
I installed the DNN 4.03 from Source, but did not run visual studio to do a build, this could be the issue. Off to try the install the package....
|
By jbonnie on
Saturday, April 29, 2006 10:25:04 PM
The following steps should be enough to move your application locally from a host, before database backups became a pain!
1) copy all of your application files and folders from the host to a local directory, for example to c:\backupsites\ws\30apr06
2) Create an IIS entry for a new web application and point it to your directory created in step 1 - for example, localhost\ws30apr06
3) ensure the appropriate ASPNET application has security rights to the directory created in 1
4) backup your production database and restore it locally
5) Create a local user to access the local database
6) Change the web.config file to point to the new local database
7) Change the portalalias table entry in your local db for your main site to localhost\ws30apr06
8) call up the site created in step 2 localhost\ws30apr06 in a browser and cross your fingers
|
By jbonnie on
Saturday, April 29, 2006 10:09:42 PM
I have been using DNN 3.1 with SQL 2000 for a while. With different sites on discountasp.net and webhost4life. I have started to use DNN 4.02 and 4.03 and they are running fine with sql 2005.
It has been easy to back up these sites locally and install them locally for archive and to refresh a development environment for SQL 2000.
Well, with SQL 2005 this has not been that easy, there have been other posts on this...
webhost4life supports a simple backup command that creates a BAK file that can be FT'ed and restored. Great!
But discountasp.net does not and the permissions on the site do not allow Management Studio to do a backup. Instead you have to script the DB objects and move the script locally to create the objects and THEN export the table data from the production system to the newly scripted local DB.
A bit of a pain and it has not worked for me yet!!! The local application starts up ok - but none of the module content or sub pages are shown. Instead the user is always...
Read More »
|