In-place Upgrade Vs Fresh Install 2005 From 2000
Apr 21, 2008
hello, what is the general consensus on installing SQL 2005. I usually run a backup of SQL 2000 dbs and then restore on SQL 2005 and change compatibility to 9.0. Is it the right way to upgrade? I'm only asking because I also did one db in-place to SQL 2005 and thought it went well until I browsed my system dbs. All of them are missing tables that usually appear in SQL 2005 system dbs. Other than that I haven't run into too many problems.
View 3 Replies
ADVERTISEMENT
Oct 15, 2007
Is it possible for SQL 2005 Express SP2 to ignore the UPGRADE parameter during a commandline install? We would like to use one commandline to handle both a fresh intstall and an upgrade depending on which is needed.
Does it make any difference which order the commandline parameters are used?
Do I need to write something to check if an upgrade or fresh install is needed and then feed the appropriate parameters?
Thanks
View 2 Replies
View Related
Aug 15, 2007
I've installed a test instance of SQL 2000 on a test box. I want to try the In-Place upgrade to 2005. I installed 2005 on the test box also, but have been unable to see how to perform the upgrade. I thought running 2005 setup again would prompt me for an instance name .... but it just tells me 2005 is already installed. I must be missing something simple.
View 5 Replies
View Related
Feb 19, 2008
Perhaps someone here can give me a hand with this...
I have three servers running SQL Server 2000. Two are running Windows Server 2000 SP4 with SQL 2000/SP4 and one Windows Server 2003 with SQL 2000/SP?(probably not 4). I copied the installation DVD to a network drive and successfully performed an in-place upgrade of the Windows Server 2003 machine. However, when I try to upgrade either of the other servers, I get an error indicating that I have a service pack problem.
Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Service pack requirement check:
Your upgrade is blocked because of service pack requirements. To proceed, apply the required service pack and then rerun SQL Server Setup. For more information about upgrade support, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Of course, the error doesn't indicate what the service pack problem actually is. My SQL 2005 media was probably released before SP4 was released because the Setup Help indicates that you can directly upgrade from SP3, but makes no mention of SP4. I can't imagine there are any migration problems with it since I can't find any reference to it as a problem on any SQL Server sites... So... I'm left wondering what my problem really is... :confused:
Any help would be appreciated.
View 2 Replies
View Related
Oct 16, 2007
I have just completed a default install of MS SQL Server 2005 x64 edition on a 1 processor Quad core, 8GB, Windows Server 2003 Standard x64 R2 machine in an Active Directory Domain. It has 2 arrays configured with 2) 36Gb drives mirrored for the OS as C: and 3) 147Gb drives in a RAID5 array as E: drive.
I am simply the server guy who was asked to install SQL server for some projects in the future. The company will be bring in people to to the dev.
I wanted to setup the server as best as I can and so I've been searching around for "best practices" for fresh installs.
Anyone have any suggestions on things to configure/setup to improve the performance of the default install?
In addition, I want to redirect the databases to the E: drive and separate them from the OS drive (C:). Does anyone have any information on doing this? I have searched and found a few articles, but thought I would ask first.
It is probably noticeable that I have limited SQL configuration skills.
Thanks,
A simple IT guy trying to build a system right
View 4 Replies
View Related
Aug 14, 2006
I am working as a consultant on a project to upgrade an Access 2000 db to SQL Server. My client has bought off on everything, and they're ordering a new dedicated box this week. They're getting a rackmount machine running Windows Server and SQL Server 2005.
My expectation was that their IT people would take care of administrative & security issues such as setting the machine up, installing & starting SQL Server and configuring the proper accounts. Suprisingly though, they're going to mount the machine in the rack, turn it on and let me do all of this.
I'm new at SQL Server, but I'm comfortable working with database objects (tables, views, etc...) I'm not so comfortable with the networking or administrative side of things. It took me a couple of hours to be able to connect to the DB on my desktop machine over my home network. You can see why I'm intimidated at the prospect of getting things integrated & running on a pretty large corporate network.
Maybe I'm overblowing this, but this just gives me the willies.
Are my fears justified? Am I going to be ok if I just follow the standard procedures for allowing TCP/IP connections to the server? Am I going to have to deal with firewalls? (I think I know the answer - "it depends on their network.." - that's what I'm scared of.. I don't know anything about their network, and I don't know enough about networking in general to figure things out..)
Are there any other best practices that I should follow for a fresh install?
View 2 Replies
View Related
Feb 10, 2007
Hi,
We are running a test upgrade form sql 2000 standard edition 32 bit to sql 2005 developer edition 32bit. Followed through all the steps and specified the account(SA priveleges and currently used by the 2000 version) and is the local admin on the box for the services and the setup seemed to move fine, except for when it got to the point of installing database services - This is the error message that I got:
MSSQLServer could not be started. Verify you have sufficient priveleges to start system services. The was no choice but to hit cancel and then the set up progressed with a final message of 'SEtup failed'.
Here is a portion of the error log:
Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
Database Mirroring Transport is disabled in the endpoint configuration.
Starting up database 'master'.
Converting database 'master' from version 589 to the current version 611.
Database 'master' running the upgrade step from version 589 to version 590.
Error: 946, Severity: 14, State: 1.
Cannot open database 'master' version 589. Upgrade the database to the latest version.
System Task Aggregate global counters produced an error that was not handled. Major: 9, Minor: 46, Severity:14, State:1
Error: 928, Severity: 20, State: 1.
During upgrade, database raised exception 15151, severity 16, state 1, address 01C4C50B. Use the exception number to determine the cause.
Error: 15151, Severity: 16, State: 1.
Cannot find the endpoint 'TSQL Local Machine', because it does not exist or you do not have permission.
Any help would be greatly appreciated
Thanks KR
View 7 Replies
View Related
Feb 19, 2008
Perhaps someone here can give me a hand with this... I have three servers running SQL Server 2000. Two are running Windows Server 2000 SP4 with SQL 2000/SP4 and one Windows Server 2003 with SQL 2000/SP?(probably not 4). I copied the installation DVD to a network drive and successfully performed an in-place upgrade of the Windows Server 2003 machine. However, when I try to upgrade either of the other servers, I get an error indicating that I have a service pack problem.
Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Service pack requirement check:
Your upgrade is blocked because of service pack requirements. To proceed, apply the required service pack and then rerun SQL Server Setup. For more information about upgrade support, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
My SQL 2005 media was probably released before SP4 was released because the Setup Help indicates that you can directly upgrade from SP3, but makes no mention of SP4. I can't imagine there are any migration problems with it since I can't find any reference to it as a problem on any SQL Server sites... So... I'm left wondering what my problem really is...
Any help would be appreciated.
View 6 Replies
View Related
Feb 22, 2008
Hi Everyone,
I was playing around with SQL2k5 Express, but decided to download Enterprise using my MSDN subscription. I installed it, but none of the services are running. I don't understand why?
I've checked the requirments and I notice that Vista x64 is not on the list for compatible OS's.
I do get this when trying to install:
- SQL Server Edition Operating System Compatibility (Warning)
Messages
SQL Server Edition Operating System Compatibility
Some components of this edition of SQL Server are not supported on this operating system. For details, see 'Hardware and Software Requirements for Installing SQL Server 2005' in Microsoft SQL Server Books Online.
Also, during the install, Componoents to Install: All the services are greyed out... is that because they can't be installed or because they're going to be installed by default?
Anyone else have it running on Vista Ultimate x64? Am I doing something wrong or does it just not install on this version of Vista?
Cheers,
Mike Avelar
View 6 Replies
View Related
Aug 7, 2006
Can the SQL 2005 install upgrade from SQL 2000 handle multiple instances?
View 1 Replies
View Related
Feb 15, 2008
I am trying to upgrade SQL 2000 SP3 to SQL 2005 SP2 on a Windows 2003 server with all the latest patches. The SQL 2005 install went through like it was supposed to but when it was nearly finished it gave the message:
" there was an unexpected failiure during the setup wizard. You may review the setup logs and/or click the help button for more info". I'm pretty new to Microsoft SQL so I looked at help and there was no information.
I've tried running setup again and keep getting the above error message. During the install the program says everthing is installed but I've noticed the Management Center is missing.
View 6 Replies
View Related
Jan 5, 2007
Hi,
I'm trying to Service Pack 4 a fresh installation of SQL 2000 (a named instance called 'SQLSERVER2000') and get the error "Installation of the Microsoft Full-Text Search Engine package failed. (-2147467259) 0x80004005 Unspecified Error" towards the end of the process thus I cannot service Pack my fresh installation of SQL 2000. I have done this many times before on other machines, but its not working for me this time.
At http://www.dbforums.com/ ( http://www.dbforums.com/showthread.php?t=1198047 ) someone ran into this problem and mentioned to re-install Microsoft Full-Text Search. I have followed the article http://support.microsoft.com/kb/827449 but run into problems at step 2C. At step 2C it says to start the Microsoft Search service via the Services console, but Microsoft Search was nowhere to be found.
Going back a step to Step 2B it says that all registry keys that were previously-deleted are now available and the previously-deleted 'MSSearch' folder is recreated. I took a look, but both the keys and folder WERE NOT there.
It is a fresh OS installation of MS Windows 2003 Standard SP1, 768MB RAM and is running fine.
Can you please point me in the right direction here?
Brad.
View 3 Replies
View Related
Aug 18, 2006
Hi
We would like to install Sql 2005 Enterprise Edition (including database engine, reporting service, integration service and analysis service) as a sepearte instance on a server which already has Sql 2000 with reporting services and analysis services. We do not want to disturb the existing sql 2000 setup.
If we do that then what will happen to my earlier sql 2000 reporting service? Will it be upgraded to sql 2005 reporting service? I heard that reporting services are instance unaware application. Where will be the default reporting service database available?
Please help us.
Regards,
Sankar N
View 1 Replies
View Related
May 10, 2007
Hi,
While we choose in-place upgrade for upgrading to SQL Server 2005 from SQL Server 2000, does it actually change the code in Stored Procedures/functions also?
e.g. if I have *= in some old procedure does it change it to INNER JOIN while migrating?
Please help me on this ASAP.
Regards,
Rahul
View 1 Replies
View Related
Jun 19, 2007
This may be very obvious and when I get to the first test server I will find out, but I only have a new installation of SQL2K5 so far to test with. I have several databases that need to be upgraded to run on 2K5, but the application requires them to run in 8.0 compatibility. Does this mean that an in-place upgrade is not an option?
I apologize if this is a silly question, but I have not yet found the answer specifically.
Thanks very much.
View 4 Replies
View Related
Jun 21, 2006
I have two software products that are accessing the same MSDE Database instance. I recently upgraded the MSDE instance to SQL Express using the in place method. The upgrade runs with success. However, one scenerio is breaking both software products.
1. Product A is not installed
2. An older version of Product B which uses MSDE is intalled.
3. I upgrade the MSDE instance to SQL Express
4. An older version of Product A is installed that uses MSDE.
Note: At this point the install of product A attempts to install an MSDE named instance that is the same as the upgraded instance
5. The install of Product A fails and corrupts the registry keys
6. Now my SQL Express named instance is corrupt and product B can not find the database instance.
Question: Can MSDE and SQL Express run side by side with both having an instance with the same name? I am pretty sure that the answer is going to be No.
If not, how can I prevent this scenerio from occurring. I'm thinking that I will have to do a side by side upgrade creating a new instance with a different name. Then I will have to direct both products to the new named instance. Any ideas or suggestions?
View 1 Replies
View Related
Oct 31, 2007
New ssrs istall. I think they loaded sp2. It's a cluster, but ssrs was not clustered (I think)
When I attempt to open report manager, i just get
SQL Server Reporting Services
Home
with no option for creating a folder etc, like i have on development
When I attempt to deploy to ther server I get :
Deploying to http://amsqlclusterxx/reportserver/
Error rsItemAlreadyExists : The item '/Retailer' already exists.
How do I create an ssrs reports folder?
Also, and this is strange, but in vs.net I had to create a new shared datasource after removing the old one on the report with the same name. The report renders fine when I do an f5 pointing to a new datasource, but I no longer have the RUN "!" icon available while in the data tag to run my query. Why is this?
Thanks for any help or information.
View 1 Replies
View Related
Dec 11, 2007
Hello,
I have a project where I have to upgrade SQL 2000 to 2005. When we are upgrading we are going to move to new server so server name will change. Most of our applications have a hard coded connection string. Applications are developed with Classic ASP, .NET 1.1 and 2.0 as well.
Now the question is what is the best way to do this? Changing all the connection string will be a very painful task as we have many applications.
Can anyone suggest a way where we can achieve this without changing all the connection strings?
Thanks in advance.
Tareq
View 5 Replies
View Related
Oct 24, 2007
what are some of the issues that we might face while upgrading from SQl 2000 to SQl 2005? Actually I have to create upgrade plan for path from MS 2000 to MS 2005.
Any suggestions will be appreciated.
Thanks
View 1 Replies
View Related
Nov 27, 2007
Hi,
I was wondering if anyone could point me in the right direction for upgrading from SQL 2000 to SQL 2005?
I was under the impression that it was as easy as following an upgrade path after popping in the CD, but I realized it's not.
I'm a Systems Administrator who has installed both version in stand alone systems, but never tried an upgrade.
Thanks for your help.
View 2 Replies
View Related
Feb 4, 2008
Hello,
I would like to upgrade sql server 2000 to sql 2005. So Can I install the sql server 2005 on the same server where sql 2000 is already running and then use the database upgrade wizard. Or should I install the sql server 2005 on a different server.
Thanks
View 5 Replies
View Related
Aug 9, 2006
I have a sql 2000/2005 side-by-side install on a single server. I right-click a sql 2000 database, select All Tasks, and the Copy Database to upgrade a sql 2000 database. In the "Copy Database Wizard" I see the message:
"To use the detach and attach method SQL Server Agent must run under an Integration Servicers Proxy account that can access the file system of both the source and destination servers."
1. What does that mean?
2. I decided to click "Finish" in the wizard, and the database copy seemed to work fine. Whaterver 1) means does, by default, the SQL Server Agent already run under this "Integration Services Proxy" account. (Rememberr the upgrade process did work).
TIA,
barkingdong
View 2 Replies
View Related
Jul 17, 2007
Hey Guys,
Looking for some type of solution on this issue. I'm going from SQL2000 to SQL2005 and I run the upgrade advisory tool and all and I'm going through the procedures of getting our SQL server updated to SQL2005, when I attempt to run that analyzer to take a look at how well the migration will go. I get a timed out error message on the fallowing.
ORDERBYORDINALS
FTCATPROPITEMCOUNT
OLDSYSTEMTABLES
DROPSYSOBJ
HOSTIDRETURN
FTPROPS
QRYGOVCOSTLIMIT
FTCATALOGNAMERESTRICTION
SPCONFIGURE
INVALIDCHAR
OPENXMLWITH
XPAGENTPROXY
UPDATETEXT
SPHELPTRIGGERNEWCOL
DISKINIT
SYSPERFINFO
DEPRECATEDSP
OLDDBCC
ORDERBYALIAS
Exact error message and its always the same for each entry.
"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding"
Any help in this are would be greatly appreciated, all other issues have been resolved I'm just stuck on this and I don't want to upgrade until the advisory tool gives me the ok to.....
Thanks in advance.
View 2 Replies
View Related
Oct 5, 2006
All,
I am looking for upgrading SQL 2000 databases to SQL 2005.Has anybody got a detailed plan /Documents for doing so?.
Thanks and Regards
Avijit Macker
View 3 Replies
View Related
Sep 23, 2006
I am in the beginning of upgrading a SQL 2000 DB on a Small business server to a 64 bit 2005 DB on a new box. Is my best method of upgrading to use the "copy" DB function in 2005? If so, what do I need to do to install the management tools on the 2000 box - since this is a 32 bit edition, and I have the 64 bit media?
View 1 Replies
View Related
Mar 7, 2008
I got a requirement to upgrade only One SQL 2000 to SQL 2005 server. i did check that there are only databases in this server along with Linked server. I am looking for a best practice document for SQL upgrade and any thoughts or experience any one has faced during upgrade.
Other question is what about if there is a DTS on the server. right now on this particular server there is no DTS but in coming weeks i may need to upgrade other server which is having DTS as well. I have worked alot on SSIS packages but want to see if DTS will be converted to SSIS packages or i will have to manually do it.
Thanks
View 3 Replies
View Related
Apr 2, 2008
Hi,
We have 2 .net 1.1 applications using Microsoft SQL Server 2000 Enterprise Edition. To connect to database we are using nHibernate 0.6 for one application and Microsoft Enterprise Library Data Blocks Ver 1.0 in another.
We are planning to upgrade SQL servers of both applications to SQL 2005 Enterprise edition and retain .net 1.1 framework. Are nHibernate 0.6 and Microsoft Enterprise Library 1.0 data blocks compatible with the SQL 2005? Are any upgrades required for these as well?
We ran SQL upgrade advisor report on these applications, there weren't any changes to table/ stored procs suggested. Could that mean that the existing table design and stored procs are compatible with SQL 2005?
Thanks in Advance,
Abhijith Bharadwaj
View 1 Replies
View Related
Mar 9, 2008
Hi all,
I just ran sql upgrade advisor and got the following message:
"You can use SQL Server 2005 tools to edit your existing DTS packages. However, upgrading or
uninstalling the last instance of SQL Server 2000 on a computer removes the components required
to support this feature. You can retain or restore these components by installing the special
Web download, €œSQL Server 2000 DTS Designer Components,€? from the Microsoft Download Center
before or after you upgrade or uninstall SQL Server 2000."
I do have several DTS packages in my sql server 2000 database. does that mean if I upgrade my current 2000 database to 2005, those dts will be gone. But I can download sql server 2000 dts deginer components on our new sql 2005 database server before I upgrade. Then when I restore my sql 2000 database on our new 2005 server, eveything would be OK? I am not sure if my understanding is correct.
My advisor is on my local computer and I am running analysis against a remote database(on our intranet),€œSQL Server 2000 DTS Designer Components,€? should be intalled on my local computer or remote database server? what steps I should take in order to retain my dts package or transform it into something else?
can you shed light on me?
Thanks.
Betty
View 3 Replies
View Related
May 7, 2008
I am going through upgrading our current installation of SQL 2000 to 2005. When I install 2005 it doesn't seem to upgrade the server, but only installs the server tools. Do I need to completely remove 2000 in order to upgrade? Thanks!
View 4 Replies
View Related
Aug 17, 2005
Where can i find some reference material on how to upgrade to 2005 in a replicated environment please?
does anyone know what order i need to tackle the servers, is it likely to be the same as the Service Pack process?
cheers
View 3 Replies
View Related
Jun 17, 2008
Hi all,
Recently, I upgraded one of our database servers from SQL 2000 to SQL 2005. At the moment, all the databases are in 80 compatibility mode. I upgraded them based on the false pretenses that I could perform online reindexing right off the bat. Apparently, that isn't the case, and it requires switching to 90 compatibility. My question is if I switch to 90, will all indexes be invalidated/unusable? Or will I be able to switch to 90 and perform the online reindexing right away with no downtime?
We have a few 24/7 production VLDB's in the mix (one of which is on this newly upgraded server), and only reasonable downtime is possible. The largest window of downtime I have is about 10 PM - 5 AM with prior notice.
The upgrade was performed using SAN-based LUN's with a detach/reattach.
Thanks,
Matt
View 11 Replies
View Related
Apr 5, 2007
Hello
Server Details:
OS => Windows Server 2003
SQL => SQL Server 2005
Client Machines:
OS => WinXP sp2
SQL => 2000, 2005 express
The developers at work connect remotely to the server. Some of them have the "client SQL 2005 express" and others are using "SQL 2000"
Over the next week I plan to upgrade all the developers to 2005 Standard.
I have performed an upgrade of '2005 express' to '2005 standard' and encountered no problems. However I have no experience upgrading the 2000 client.
Can anyone suggest a strategy (fresh install/upgrade)or highlight any pitfalls that I should avoid.
Thanks in advance for any help/suggestions offered.
Regards
Toby
View 1 Replies
View Related
Jul 30, 2007
Initially, the articles I read suggested that doing an "in place" upgrade is the simplest path, with the drawback that if something goes wrong, I'll have to re-install 2000. And that migrating is more difficult since I'll have to recreate all the logins , security, replication ....
Then I saw a series of posts saying migration is the best ... backup & restore (or detach, reattach) the DBs to a new instance of SQL 2005. What about the systems DBs, such as MSDB and the DTS packages ?? Also, If I migrate to a new instance of SQL, how will I re-establish the connections from other servers ? They are replicating or DTS-ing to ServerA, but now SQL2005 is on ServerASQL2005 (Same server, different instance.
In the scale of things, we have fairly simple environments, although our Production database is almost 300 Gig.
If I install a new instance of SQL 2005 on my SQL 2000 server, and migrate everything from 2000 to 2005, I now have 2 instances: ServerA and ServerASQL2005. All my other servers are referencing the original instance name of ServerA. How do I resolve that problem so that communication between the other servers will still work ??
View 7 Replies
View Related
