.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

SQL Upgrade and Migration

Posted By:      Posted Date: October 15, 2010    Points: 0   Category :Sql Server

Hi All

we are running SQL Express 2005 adn aer up to the 2Gb limit for our 2 db's. I have installed MS SCE 2010 on another server and that runs on SQL 2

We are running SQL Express 2005 and are up to the 2Gb limit for our 2 db's (so 4Gb). We need to do some work on them but work keeps failing because of the db size limit. I have installed MS SCE 2010 on another server (2k8 r2) and that runs SQL 2008. What I would like to do is rationalise.

I would like to migrate/move the db’s to the 2008 server, and don’t really know how to start.

I have also encountered a problem in that the current 2005 install which somehow has a NULL password and when I tried to upgrade to SQL Express 2008 I couldn’t proceed because of this.

I could really do with a step by step guide of the process to follow which I think will go something like:

View Complete Post

More Related Resource Links

Looking for guidance: Integrated SharePoint SSRS migration and upgrade from 2007 to 2010


Our existing prod farm is MOSS 07 with an integrated SSRS instance using SQL Server 2008, both on Windows Server 2003 64bit boxes. SharePoint databases are on a different SQL Server 2008 server.

I have built a new SharePoint 2010 farm on Windows Server 2008 R2 boxes, using a single SQL Server 2008 R2 Enterprise server as the backend for both SharePoint databases and Reporting Services (installed in Integrated mode). We are going to be using the database-attach method of upgrading our SharePoint farm.

Is there any specific guidance out there on exactly how to migrate/upgrade Reporting Services in this scenario? I've read through some of the MSDN content (How To: Migrate a Reporting Services Installation) but nothing seems to deal specifically with doing this when in Integrated mode with SharePoint. Our business heavily relies on SSRS reports in SharePoint and also shared and custom report subscriptions via email.

We do have a dev SharePoint 2010 farm in a similar configuration that I can test migration/upgrade steps. Thanks.

Upgrade XML : What the use of this file at and after migration?

What is the use of UPGRADE XML.... IS that the upgrade file is prepared at the time of MIGRATION(gradual upgrade)?

Is that we need to write the upgrade xml before doing migration :gradual upgrade?

Is that the upgrade file is used to fullfill the user request...i mean we have mapping in UPGRADE file used for finding the mapped page?


SQL 2005 upgrade to SQL 2008 R2 migration plan


Where can i get a outline for upgrading from 2005 to 2008 r2 (both standard).
The 'Copy Database' from ssms fails when it finds a database role in my 2005 database.  Not sure why.
I tried an IS project to transfer logins and it also fails.
I assume i need to transfer logins w/ sids or they won't match if i detach and copy files.
I had fewer problems moving from 2000 to 2005, sorry, frustrated.

SharePoint document migration challenges when migrating files and folders

There are several challenges when migrating documents to Microsoft SharePoint. While these challenges can be overcome, they are a real pain if the migration source, content and file systems are not SharePoint friendly.

Best Way to Upgrade Using Web Setup Project


Hi there,

I am using VS2005.

I don't have much experience with web setup projects, but I now need to create a decent windows installer in order to allow customers to install one of our web applications. I have created a simple web setup project and it works fine, but not when it comes to upgrades of the application.

If for instance I install version 1.0 on a machine, and then later I try to install version 2.0, I don't seem to have the control that I would like... I can specify in the web setup project that the installer must enforce an uninstall of previous version, but then all application files and logs are uninstalled as well. If I let the application just install itself over the older version, it seems to leave some old DLL's there - it then causes issues in the application because DLL version conflicts.

My basic requirement is that I would like th installer to upgrade the old version with all the files required, but leave any application and log files in tact - this way the customer won't have to reconfigure the application after install.

What is the best way to handle this?

Migration from ASP.NET 3.5 to 4.0


So, I just recently started to migrate my website from 3.5 to 4.0.   I am running in a bunch of issues but mainly 2 so far that have me stumped.

1. I have a custom URL rewrite module that I use, and it seems like it's being ignored to some extent.  It works fine if I run it through Visual Studio 2010 debugger, so I have no idea why it's not being fired. 

2. In some of my pages, I reference a BasePage class instead of System.Web.UI.Page.  The ones that reference this BasePage class works fine, but when I use System.Web.UI.Page, I get : Object reference not set to an instance of an object when I try to create an object.

Any ideas? 

Migration to .Net 2 and includes



I'm currently having a problem with one of our old .Net 1.1 applications. For generating the user interface, a lot of incude statements were used.

<!--#include file="includes/header.aspx"-->

In these includes, the variables from the parent files are used.

Now I have to use at least .Net 2 and Visual Studio 2010. The problem is that VS tries to compile these include files, which of course failes.

Is there any way to restore the old behavior again?



Who Goes There?: Upgrade Your Site's Authentication with the New ASP.NET 2.0 Membership API


Here Dino Esposito and Andrea Saltarello cover the plumbing of the Membership API and its inherently extensible nature, based on pluggable providers. To demonstrate the features, they take an existing ASP.NET 1.x authentication mechanism and port it to ASP.NET 2.0, exposing the legacy authentication mechanism through the new Membership API.

Dino Esposito and Andrea Saltarello

MSDN Magazine November 2005

Controls: Plan Your Migration to the Visual Studio 2005 Navigation Controls


Navigation is central to a well functioning Web application and it can be implemented numerous ways using today's technologies. This article highlights some of the key details of the new navigation controls that are part of the upcoming ASP.NET 2.0, and talks about how to design and implement one of these navigation controls today. This article contains a simple Web site that demonstrates the use of these navigation controls, pointing out some of the key items such as a breadcrumb control and things to watch for along the way. The article then describes how to implement a breadcrumb control today.

Dave Donaldson and Steven DeWalt

MSDN Magazine June 2004

.NET Migration Case Study: Using ASP.NET to Build the beta.visualstudio.net Web Site


When the Web site used to collect customer feedback about the Visual Studio .NET beta needed an update, the Visual Studio team saw a good opportunity to implement, deploy, and showcase a real-world site using .NET technologies. This article covers the migration of the Web site, beta.visualstudio.net, from components written in Visual Basic 6.0 and ASP hosted on Microsoft Internet Information Services (IIS) 5.0 to ASP.NET and the .NET Framework. The choices of technologies to be incorporated, along with issues such as validation, security, and authentication, are all discussed. Both existing components and the new components written in JScript and ASP.NET that were used to migrate the site are also explained.

Jay Schmelzer

MSDN Magazine September 2001

An example of packaging web application containing database upgrade SQL file

A few months ago, we have a blog talking about extending the web publishing pipeline to package database project deployed SQL file.  In this blog, I'll show step by step example of packaging web application with SQL Server database upgrade SQL file using Visual Studio 2010.  This way, we can generate a web package with incremental SQL script to certain database version.  The scenario may help distributions of a web upgrade package which needs to be installed on many different locations, each with their own SQL server database.   1. Create a Web Application Project 2. Add a new "SQL Server 2008 Database Project" to the solution 3. Prepare a development database, such as my test1 database as the following: 4. Right click our...(read more)

site migration


Hi we are migrating a website from a proprietary system  to a new system built inSQL 2008.

We have created a lookup table that contain the UrlAlias of every individual page and its associate id. On every page request the new system has to query the lookup table with around 6,000 pieces of rows to get its id.

Now i am afraid of the load it would generate on our server and make the system slow?

Is there any work around of doing this using rewriter, regular expression etc

How to upgrade from Windows SharePoint Services 2.0 to SharePoint Foundation 2010 after mistanely de


I need a detailed instruction on how to upgrade From Upgrading from Windows SharePoint Services 2.0  (SBS 2003 ) to SharePoint Foundation 2010.

Background of the case:

I have all my databases (STS-database and STS_Config) saved but, I forgot to save my Virtual Site )Companyweb site) and I mistakenly re-installed IIS on the SBS 2003, hence  I lost the companyweb site. Is this an issue to migrate to Sharepoint foundation 2010. The Sharepoint foundation 2010 is running on a Microsoft HyperV Server 2008 R2
Also, I have created a Virtual 2003 SRV ENT with Sharepoint Services 3.0 running on it. I also have attached my Databases STS_Database and STS_Config)... how do I get it working like a regular website. I have modified the CNAME record to reflect the new server... http://companyweb - it take me to the new site but it loads a blank page. I did create a new CompanyWeb Virtual site on the VHD 2003 server.
Your help is greatly appreciated.

Thanks for your prompt response. Nelson

FeatureInfo... Failed SiteOrphan... Failed in SharePoint 2007 SP2 migration test


Hi All,

I've just execute the C:\>stsadm -o preupgradecheck command to check my upgrade / migration process, however it come back with the following two error: 
FeatureInfo... Failed 
SiteOrphan... Failed

how shall i proceed with the migration then ?

all of the other result seems to be fine so far.


C:\>stsadm -o preupgradecheck  

SharePoint Enterprise Search Migration Tool for SharePoint Server 2010

Use this tool when you upgrade to SharePoint Enterprise Search to migrate search-related data, such as best bets, search scopes, and site collection search settings.
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend