Hi,
We have a VB application, which extracts data from SQL Server 6.5 database. Recently we upgraded our database from 6.5 to 2000.
One of the report which used to give results in Sorted order in 6.5 database, is not producing the same report in sorted order. We didn't do any change at database/application level.
As we have not made any changes at application level, I am presuming that the problem is at database level, due to this upgradation.
Can any one guide me how to rectify this problem.
As I don't have source code for this application; Is it possible for me to extract the query running for this report from database?
Hello!I would like to change the SQL server 2000 from Standard version toDevelopment edition. I have two database running on this server, bothreplicated, with few jobs, etc ... Can you recommend the easiest way to dothis? I heard, it would be as easy as, detaching the databases, deletingcurrent SQL software, installing different one, and attaching the olddatabases back. I doubt that is true, so that's why I'm asking here for anyreal-life instructions.Thanks for your input!Kind regards,Dejan--
I am planning on upgrading my existing SQL Server 7 to 2000. I plan on starting out just upgrading the SQL first, then upgrading to Win2k Server later on.
I have read some posts here with some of you having issues, etc. Based on your experiences, do you suggest, I do both upgrades together? I think it would be best to do this on a new server, and keeping everything live on the other server until I feel comfortable in moving over the data.
What files besides the database files, should I restore, if any? Are there any significant application performance issues or bugs? Should I wait to apply the first sql patch that was just released last week? What about any code that needs to be rewritten?I will do it as a test first, but any advice would be great.
We are trying to do an upgrade in place and are getting errors that it can't activate model database files. We believe it's because we move all log files to another drive and think Microsoft failed once again to recognize this in their upgrades. They made this mistake in 7.0 SP2 (the SP failed if you moved log files to alternate location) but they fixed it in SP3.
Has anyeone experieinced this problem? Is there a workaround (other than the obvious.)
We are about do an upgrade from 6.5 to 2000. Does anyone know of any material that would be of assistance to me. If you have any pointers that would also be appreciated.
Try to upgrade SQL 7 on a NT4 system to SQL 2000. Also like to upgrade NT4 to Win2K. Anyone know what's the best sequence for doing so? Thanks on advance.
What is the best way of brining a SQL Server 6.5 database to a Consolidated SQL Server 2000 environment? I tried using the SQL Server 2K upgrade wizard and it failed to import some data, which made me uncomfortable in using this tool? Is this a safe approach:
Create a database on SQL 2K and script out all the objects like tables, Indexes, views and run it against SQL 2K.
Then run the DTS to populate all the tables and you are done?
Hi, I'm looking to upgrade our old 6.5 server (running NT4) to 2000 and go to Windows Server 2003 at the same time. There are 10 or so small to medium sized DBs on here. Can anyone provide some decent links to blogs, FAQs or documentation relating to this?
Hi,I am trying to use the Upgrade Wizard in SQL 2000 to upgrade a SQL 6.5 db to2000. I am only choosing to update a single database, not system objects.The Upgrade wizard connects to SQL 6.5, checks the db, creates the db on SQL2000 with all tables and imports users from SQL 6.5. The problem comes whenit tries to bring over the actual data. I get an error:"Couldn't connection to the export machine!" in the out log file.The in log file reports login failed.Both SQL services were running at this point, the login via SA must beworking since it copies over the 6.5 db structure and users.The SQL 6.5 machine is NT 4. The 2000 machine is Windows Server 2003. Iwas logged in as domain admin when running this. I tried playing with the"SQLUpgrade" DSN that was created on the SQL 2000 machine to use SA orwindows authentication, both fail.Any ideas?Thanks.
Hi! If doing online version upgrade from SQL 7.0 to SQl 2000, (1) do Ineed to shut down server? (2) after upgrading, is all login and dbuser, group information, scheduled Jobs, maintenance paln... stillthere? or I have to save the info before upgrading and recreate afterupgrading? (3) any other tips I need to know? I'm doign that for thefirst time.Thanks!Saiyou
This is want happen. We have upgraded from sql 2000 sp3 to sql 2000 sp4 on an window 2003 server with sp1. Now we are getting this error. ERROR: 17805, SEVERITY: 20, STATE: 3 INVALID BUFFER RECEIVED FROM CLIENT..
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
I am upgrading a SQL7 std to SQL2000 std The upgrade process fails in the upgrade.sql step. With no meaningful error messages. All services that may use the db are stopped, the net is disabled so this server is stand alone, nothing can be accessing the db !
I cannot find any log output, from the upgrade so I dont know whats causing this. Has anyone any ideas ?
How do I upgrade my local sql server 7 to sql 2000 ? Do I just put in the sql server 2000 CD and run it or is there an upgrade CD ? I have lots of stuff on my sql 7 and don't want to lose it.
I've couple of questions about Sql Server 2000 and would greatly appreciate, If somebody out there, please answer to it.
Questions:
I've a SQL 7 server dump file and I was wondering, If I can directly load this file into SQL Server 2000? If yes, Would this call a Upgrade of sql 7.0 database to SQl Server 2000? Or this is just a backward compatability support in 2000?
Well the main objective of this is, We are planning to upgrade one of our production SQL 7.0 server and I was wondering, If we can just take the SQL 7.0 dump file and load it into the SQL 2000 Server? If yes, What are the downgrades of this and if no, Should we upgrade the sql 7.0 server itself and along with it all the databases sitting on it? Please shed some light here.
I started with a SQL 7.0 installation and installed an instance of SQL 2000. The default instance is SQL 7.0 as expected and both run fine. However, now I'd like to upgrade the SQL 7.0 instance to SQL 2000, but the setup procedure on the install CD only allows you to upgrade/modify the SQL 2000 instance. It seems as though once you've chosen to install SQL 2000 as an instance, you do not have the opportunity again to upgrade the SQL 7.0 instance in place. I tried to remove the SQL 2000 instance and reinstall 2000, but the procedure does not give you the opportunity to upgrade the SQL 7.0 instance -- only to modify the programs installed. Any suggestions?
(I could use the Copy Database Wizard to move all databases along with associated stored procedures, logins, etc., but then I'd have to mess with DTS packages, etc.)
I have tried several SQL 2000 upgrades from SQL 7.0 SP3 , NT 4.0 SP6a and numerous hotfixes.I have not had one go through the first time without a problem. These are inplace upgrades, not an install of a new instance.
Number one was the upgrade failed with "The ordinal 105 could not be located in dynamic link lib opends60.dll. To work around this I had to back out our two hotfixes (MS01-032, a security hotfix and the SQL profiler hotfix).
Number two was that MSSQLSERVER would not start before running MESSSAGES.SQL causing setup to hang. To work around this M$ told me to invoke SETUPSQL in debug mode and step through the upgrade and manually start MSSQLSERVER before MESSAGES.SQL was run. This worked and I was able to complete the upgrade successfully.
Number 3 occurred when SETUP could not find MASTLOG.LDF and died. When I first started running 7.0 I decided to move all logs to our separate log device even if they were truncate log on checkpoint. I know, it sounds stupid. I have since stopped this practice. I was able to move MASTLOG.LDF back to the same device and directory as MASTER.MDF and things worked fine. I feel setup ought to look for the logfile in the location specified on the MSSQLSERVER service startup parameter and not assume it's location.
Fortunately all of these upgrades were on test boxes or non-essential servers. However, I am very worried that new problems are going to crop up at each upgrade. I always ghost all volumes before an upgrade and also have good backups, so falling back is not a problem. Has anyone else had these kinds of problems with upgrades? Remember, I am talking about an upgrade not a detach all dbs, uninstall 7.0, install a new instance and reattach all dbs. Though this is something I can fall back on. Detaching and reattaching all DBs would be allot of work with saving logins and all.
I would appreciate any help or suggestions?
Steve Rinehart Battelle Memorial Institute Information Management Technology Group, Network Computing Systems (614) 424-6543
I'm running the SQL 2000 upgrade wizard and this error came up in the final phases of the upgrade to SQL 2000. The phase is doing the Export Import of the Table data:
Error: Couldn't connect to the ADMIN$ share on the export machine. Verify that the MSSQLServer Service uses a NT Domain account that is part of the Administrator's group of the export machine and that both machines are in the same domain.
I've checked and service account are in the local admin group and both are in the same resource domain. The service account is in the accounts domain.
I have SQL server 6.5 with service pack 5a. Another machine with W2k and SQL server 2000 with SP3 and disables cnv6x70.dll.
Currently we have SQL 7 standard server with 100 user CALs. We are planning to upgrade to SQL 2000. What happens to the CALs we have already purchased for SQL 7? Do we need to pay again for user CALs on SQL 2000? Or can we pay just for upgrade the server software?
We've some of the boxes are SQL Server 7.0 with 65 compatability and SQL Server 7.0 with 70 compatability. Now we are planing to upgrade to SQL 2000 with 80 compatability. My question, how much complicated it is? Is there any code changes to do in Stored Procs or Triggers or other? and what are the differences?
If lot of code changes, is there any tool to scan stored procedures? (As we've more 5000 Stored Procedures)
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.
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.
Hi AllI know that if SQL 6.5 was on a server and you then install SQL 2000 on ityou get the wizard option to upgrade an SQL 6.5 DB to 2000, but I don't havethe luxury of this.I have an SQL 6.5 DB, which I want to convert, but only SQL 2000 on myserver.Do you know what options I have available to me to perform this upgrade withwhat I have? Are there any free external tools that can do this conversionfor me other than the switch wizard?Thanks
We have Sqlsvr 6.5 under NT4. We want to upgrade the database toSqlsvr 2000 under windows 2K. Is there any way we can do this bycopying the database to the win2K computer?? At any rate wouldsomeone explain how to go about updating this. I know nothing aboutsqlsvr anyversion but do need to know.TIA
