A little something about everything

This method can be used to fix duplicate content errors and make it so google only indexes one version of your urls, which will prevent you from getting a negative modifiers.

In order to do this you have two options.

1. Use the proper canonical tags, for example place the following code at the top of your website:
   <link rel="canonical" href="http://(yourdomain).(tld)/Your-Special-Directory-With-Whatever-Case-You-Want" />
2. Use the following script to automate the process and only allow lower case urls to be viewed on your site, create a global.asax file and place it in your site's main directory. 
   <script language="C#" runat="server"> protected void Application_BeginRequest(Object sender, EventArgs e) { if (Regex.IsMatch(HttpContext.Current.Request.Url.ToString(), @"[A-Z]")) { // Lowercase url String lower = HttpContext.Current.Request.Url.ToString().ToLower(); // Redefine response HttpContext.Current.Response.Clear(); HttpContext.Current.Response.Status = "301 Moved Permanently"; HttpContext.Current.Response.AddHeader("Location", lower); HttpContext.Current.Response.End(); } } </script>

If you plan to use both methods be sure to use only lower case for your canonical tags or you will end up with problems.

Update the if error section to retry after waiting for 1000ms, then attempt the request again, for example replace:

alert("Google Feed API Error: "+result.error.message)

with

function sleep(ms) { var dt = new Date(); dt.setTime(dt.getTime() + ms); while (new Date().getTime() < dt.getTime()); } sleep(1000); var thisfeed=(!result.error)? result.feed.entries : ""

In order to fix this bug you can simply run this command on the effected database after you have used the backup (sql2000) / restore sql2005/2008) or detach attach methods.

command to run:

 exec sp_change_users_login'Update_One','dbusername','dbusername'

Replace "dbusername" with the problem user account. both should be the same.

This will remove the ghost user from the sql 2000 server and replace it with the new user on your sql 2005 / 2008 server. Be sure to have the user created before running this command.

Errors associated with this are as follows:

"login name must be specified Database user"

"The database principal owns a schema in the database, and cannot be dropped"

"user group or role already exists in the current database"

"can't delete sql user in database"