|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Monday, November 01, 2010 6:18 PM
Points: 7,
Visits: 28
|
|
| This article certainly highlights the difficulty of performing quality technology services when basic communications skills are substandard. This article is a difficult read, not for the technical content, but for the grammatical errors, poor sentence structure and even spelling mistakes. While the author's technical skills may be adequate, writing such an article to build a reputation, gain clients and impress others may have a very different effect. Such an article should demonstrate a certain skill level in two areas, technology and communications. This author has one. We should, and this board should, strive for excellence in both.
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, May 31, 2007 7:58 AM
Points: 1,
Visits: 1
|
|
Nicely written article, gives a fair idea about SQL database upgrade. keep it up !! Mamta 
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Thursday, July 05, 2007 6:14 AM
Points: 10,
Visits: 1
|
|
The article is complete and it asissted me in doing the upgrade. I've asked my fellow consultants in my company to consider this article as the best practices for our team. Thanks for the hardwork that was necessary to create this article!!
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Wednesday, February 09, 2011 2:35 PM
Points: 7,
Visits: 17
|
|
Besides Sachin's guide, I'm also reviewing book "Microsoft SQL Server 2005 Unleashed" (SAMS pub) for the proper upgrade path, and find the information about Fulltext indexes conflicting. While Sachin states Fulltext indexes should be completely removed before upgrading and recreated, the Unleashed text states these are taken care of in both Side-by-Side and In-Place upgrades: From page 208 for Side-by_Side: "You might be wondering how the [Copy Database] wizard handles your full-text catalogs. Rest assured, they are imported by default during either a restore, an attach, or via the Copy Database Wizard..." From page 217 for In-Place: "...When your upgrade of the database engine is complete, it is recommended that you perform the following on all databases (also recommended for side-by-side migration): -Repopulate your full-text catalogs. (This is automatically done for databases where Full-Text indexing was enabled prior to the upgrade.)..." I did not find any reference in the Unleashed text about removing the full-text indexes prior upgrading at all. What gives??? Thanks for your replies. Great article by the way. Charlie S.
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Sunday, July 01, 2007 12:42 AM
Points: 1,
Visits: 1
|
|
Article is well structured, concise and to the point. It reflects a competency level of an author in this topic. I find it interesting and easy to digest inspite of a fact that the database upgradation has never been my cup of tea.
I really wonder what would happens to a pre-compiled stored procedures which have been created by a user? Would there be any impact on those stored procedures ?
Keep writing more stuff (:-
Regards Dinesh
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, October 25, 2007 2:18 AM
Points: 7,
Visits: 29
|
|
[font=Verdana]Hi,
I restored SQL 2000 Database to SQL 2005 and wanna "Repopulate all Full Text catalogs".
Please let me know how to do this.[/font]
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Wednesday, February 08, 2012 9:56 AM
Points: 1,
Visits: 33
|
|
The document is excellent!!!
I need something like that, but i need to do a Side by Side Migration.
Could you give some tips, best-practices,...
Thank you;)
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Saturday, July 18, 2009 3:10 PM
Points: 4,
Visits: 18
|
|
Hi,
Planning sql server 2000 upgrade to sql server 2005. I did a test side-by-side upgrade, installed the 2005 instance on the same box. Realized that the databases on the 2000 instance were automatically replicated to sql 2005. I did backup on sql 2000 and restored to sql 2005. Realized that when i dropped the DBs in the 2000 instance the same DBs in the 2005 instance were also dropped.
Please help
|
|
|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Tuesday, May 17, 2011 9:15 AM
Points: 44,
Visits: 3,626
|
|
In side by side upgrade, sql server 2000 database never gets upgraded automatically. SQL 2000 Database need to be manually ported to the new verstion.
I think, you viewed the old instance of SQL server 2000 using SQL server Management studio and thought it got upgraded. And then from Enterprise manager you droped the same database .
I hope you have the backup. Restore the backup in the new instance you created and then change then compatibility level as mentioned in the document.
Let me know incase of any further query.
Regards Sachin
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Saturday, July 18, 2009 3:10 PM
Points: 4,
Visits: 18
|
|
Thanks Sachin,
I realy apprecaiate your timely response. I did a restore to ANOTHER location, dropped the old DB in sql 2000, and the instance in 2005 was dropped asl well. I will appreciate if you give me a step by step guide of how to do side-by-side upgrade using BACKUP of the DBs in the 2000 instance and RESTORE to the 2005 instance.
I have two issues raised by upgrade advisor. They are:
1. Outer join operators *= and =* are not supported in 90 compatibility mode
2. Upgrading will cause Full-Text Search to use instance-level, not global, word breakers and filters by default
3. Column aliases in ORDER BY clause cannot be prefixed by table alias
I will appreciate a quick responce. I am already in the project and need to resolve these issues.
Regards,
Victor
|
|
|
|