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 »
|