There are times where you might be moving a DotNetNuke® database from one development machine to another.  In these cases, you might also use the data SQL user for your development.  Depending on how you move your databases, this user will still exist in the database itself, but will not exist in the new SQL Server instance.  You might think, “That’s easy! I will just add the missing user.”  Unfortunately, when you do and try to map that user to the imported database, you’ll get a message similar to the one below:

Create failed for user ‘’.

User, group, or role ‘’ already exists in the current database.

Unfortunately, this “existing” user doesn’t really exist.  We need to drop the user from the imported database.  You might try the DROP USER command, but that’d likely greet you with the following error:

Drop failed for user ‘’.

The database principal owns a database role and cannot be dropped.

In many...

In order to round myself out, and spread the DotNetNuke and ODUG word, I attend other user group meetings and events.  Last night, I went to the OPASS meeting.

I ran into something of a usability issue when installing a fresh copy of DNN 4.09.00...

If you have ever spent any amount of time writing T-SQL, you have likely at some point come across the need to write a query that needs to check or compare the value in an NTEXT field. Prior to SQL Server 2005, that wasn't possible. Here is how to do it now...

Well, I just got back home from SQL Saturday in Heathrow, FL. It was a really great event! For it being the first one, it was well organized and had a great array of topics.

There are great many things that we realize we take for granted when hand-coding database updates. For instance, in the SQL Server Management Studio (or Enterprise Manager), we often right-click something and then let a wizard walk us through some steps and... POOF! Your database is updated!

If you are anything like me, you always want to find the most efficient way to do something. For instance, you cannot restore a database without first stopping all of the processes that are currently running under the database. Here is where a neat little snippet might be useful to you!