I run into a problem which I cannot connect to the database using SQL Server 2000 Enterprise Manager. The SQL Server 2000 was working well until I hook a SQL Server 7.0 application to it. The error message: "General OLE Error 16386, You must upgrade your SQL Enterprise Manager & SQL-DMO (SQLOLE) to SQL Server 2000 (SQLDMO) to connect to this server". I checked fixed in the sp1 for SQL Server 2000, and found no entry. In MS support website and found nothing. Need help from someone who has experience on this. Thanks in Advance.
Hello, i have a question that the sql server 2000 is install in window 2000 server. If i want to update to window 2003. Is that any problem in sql server 2000. I am worry about whether we will have problem after update. What i need to do? Many thanks.
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.
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)
We're upgrading a SQL Server 2000 cluster (Active/Passive) running on Windows 2003 Server 32 - bit Standard to a SQL Server 2005 Cluster running on Windows Server 2003 64-bit Enterprise. Our existent cluster's databases are residing on SAN. We can't purchase new hardware and we have no spare hardware. We also need to move from Windows 2003 32-bit Server to Windows 2003 64-bit Enterprise Server at the same time. We want to keep downtime to a bare minimum.
What we were thinking was the following steps... Anyone try this?
1. Break the link between the servers. Or should we just evict the passive node?
2. Install a fresh copy of windows 2003 64-bit server on one side along with SQL Server 2005. While this step is running, the active node would still be live on Windows 2003 32-bit Server and SQL Server 2000 serving our customers.
3. Bring the active server down.
4. Create new cluster on the newly upgraded server and assign the same cluster name and IP as the original one.
5 Bring the luns from SAN to the newly upgraded server and initialize SQL Upgrade
6. As a final step, the old active node will be rebuilt, we would install a fresh copy of windows 2003 64 - bit server on it and sql server 2005. At this point we would bring it back into the cluster and the cluster would be complete again.
I am currently using sql server 2000 and I have just installed sql server 2005 in a separate box that will be used as the production server so I will be upgrading to the new database server soon.
I was reading the upgrade options for this situation and one option is to detach the 2000 database, copy the mdf and log files to the new server and attach it to mssql 2005. Another option is to recreate the tables, views, etc. and export/import the data to the new server.
I would like to ask what the best option is for this situation because I am not sure what the advantages and disadvantages of just detaching/attaching and recreating the database in sql server 2005. If I just detach/attach the database, will there be any disadvantage in the performance because the database files were created in 2000 and is functioning because of backward compatibility in 2005? Would it be better to recreate the database in 2005 and import the data from 2000 so that the database would be running in a way that is designed for 2005?
I am not really sure of the differences of these upgrade options so any ideas would be greatly appreciated.
Hello, I have sql server 2000 personal edition on my PC and I have just got a 2005 DVD. I tried to install it but it is not working. I don't know how to manage my databases. As if there is no graphical managemnt tool. The 2005 is also Personal edition. I reinstalled the sql 2000, and now I'm trying t upgrade to sql 2005, but still don't know how to do that. Please someone help me!!!!!!!!!!
Probably this question has been asked hundreds of times and yet netsearch has not generated satisfactory enough answer, at least, to me.And OK, let's assume your organization has more than 200 employees,just one measure to indicate that it's not small and data processingneeds are quite extensive (for both OLTP and OLAP).We've heard so much about concurrency support, stability andperformance. Are there any real persuasive paper out there to talkabout it? Now, let me also put it in another perspective, say, you'rea Microsoft sql server sales guy or gal for that matter for newaccounts. What you got?Thanks.
This question probably has been asked many a time. And yet I feel itis still relevant for one thing a search on this NG does not produce adesirable answer.It is kind of disappointing that MS would not be able to transfer ERrelationship from an Access db to a SQL Server 7/2000-based one, theupgraded db/imported tables sitting on the SQL Server would not havePKs, say, you have 100 user tables, you have to first recreate PKs foreach of them then set up relationship between/among them, quite timeconsuming. Do you have a better way?Along the same line of the task, what options out there for convertingAccess Modules into SQL Server-based Stored Procedures and/or UDFs?The manual option is sure there, third party tool? I wouldn't trustthem that much though.TIA.
I have a production failover cluster running SQL Server 2000 at SP3that I want to upgrade to SP4. I do not have a test failover clusterto test with so I need the install on the primary server to work thefirst time. Per the information I have I just install the patch on theprimary server and it will install both on the primary and on thesecondary.However, I remember when I did the initial install and it failed. Thefirst problem traced to the fact that the install uses temporary filesunder the profile of the installing administrator and the id had neverlogged into the second server so the install failed on creating thetemporary file. The was a second problem that related to an OS featurethat had to be off for the install to work.If anyone out there has done this upgrade and remembers encountering aproblem and its fix/workaround I would appreciate a head up warning.Thank you-- Mark D Powell --
I've inherited 6 sql server 2000 boxes. I've upgrade 3 with no trouble. now I have one that gives the message : "your upgrade is blocked because of cross-language compatibility rules. For more information about cross-language support, see the version..."
all servers are 2003, sp2. All SQL is Enterprise edition, default language is "english". even the collation order is the same. why the cross language message? Any help would be good else I'll be forced to rebuild the DB and load application again. ugly!!
We have a product which uses SQL Server 2000 Enterprise Edition with Per Seat licensing option. Going forward with a new release of the product, we intend to upgrade to SQL Server 2005. Till now our product was being used in non web based scenarios so the Per Seat licensing option helped our case. In the upcoming release which would use SQL Server 2005 we need to break off from the non web based scenario as the product would use SQL Server over internet. So isn't it correct to go for the Processor based licensing instead of the Per seat licensing ?
If so then what would be the ideal manner to upgrade the license from Per Seat (in SQL Server 2000) license type to Processor based (in SQL Server 2005) license type ?
I have heard of Software Assurance providing assistance in version upgrades. Would it help in case I need to upgrade from one license type to another ? Or is it applicable only in case of upgrade where the license type is fixed ?
My question might be a little bit unusual, but is it possible to upgrade SQL 2005 Express (the free version of SQL) to SQL 2000 Server without any loss of functionality?
Where do I have to pay attention to when doing this?
Currently we use SQL 2K SP4 and snapshot replication with a Central Publisher with Remote Distributor toplogy.
I am looking to upgrade or migrate our SQL servers to SQL 2005 and was wondering what is the best way to do this for our replicated architecture?
Is the best way to run the SQL 2005 Upgrade on all 3 servers (publisher, distributor, subscriber) and should it automatically upgrade the servers including the replication components? Is there anything i should consider/watch out for when doing the upgrade and it involves replication (namely snapshot replication)?
I would like to upgrade a production active/passive SQL Server 2000 cluster to SQL Server 2005.
I've read all of the documentation I could find, and doing an in-place upgrade seems to be the way to go. (Despite the fact it scares the hell out of me.
But throughout all the documentation, I've yet to see some simple and fairly important questions answered.
How does the process of upgrading SQL Server work when you're dealing with a cluster?
Do you upgrade one machine then the other? If so, do you upgrade the active node first, or the passive node?
What happens if you're forced to failover from one instance to the other before you've had a chance to upgrade both to 2005? In other words, you failover from 2005 to 2000. Would that even work?
What happens if your upgrades fails for some reason? Is it easy to rollback the installation? If not, will reinstalling SQL Server 2000 cause any issues? Will it remember the previous configuration and simply fix the broken install?
If there was a view that joined 2 tables and I accessed the view the 2 ID fields in the view would still have the AutoIncrement attribute still set to true so that I knew those were Identity fields.
In SQL server 2005
I dont' know why but if you reference a View that has Identiy AutoInc fields in ADO it doesn't keep those properties.
Also for whatever reason we Set the ID field to 0 to let ourselves know its a new Record. SQL 2000 let it happen and assumed it to be null where as By Setting the ID to 0 in SQL 2005 causes it to blow up on me.
Is there some sort of setting in SQL that can make SQL 2005 work like SQL 2000 in these two instances...
I recently upgraded my MSDE server to SQL Server 2000 database. After the upgrade, I see, every minute,in the logfile that the database is starting whilst in Enterprise manager the database is up and running. I would be grateful if you could bail me out of this anomaly.
I cannot connect to the remote SQL Server 2000 running on this machine that has just been upgraded to the W2003 server. Everything worked perfectly before the upgrade on W2000. All the logins, firewall setting stayed the same. Can ping the machine. But when trying to register/link, or connect thru ODBC, I got the error SQL server does not exist or access denied. We don't have SQL server SP3 installed.
I'm trying to upgrade from SQL Server 2000 to 2005. The problem I am having is that when I try to attach the existing db files I get a message that says "database cannot be upgraded because it is read only or has read only files...."
Thing is... there is no write protection on the files.
Can anyone advise me on how to overcome this problem so that I can attach the db, please?
We have 3 MSDE databases (3 seperate servers) which we need to make into one Sql 2000 server (new server). How is this done? Can't find anything clear about this.
We are going to upgrade one of our SQL Server 2000/Win200 instance to SQL Server 2005/Win2003. Currently, the SQL Server 2000 which contains about 30 database. This is my plan:
Install SQL Server 2005/Win2003 on a new instance Backup SQL Server 2000 database instance (how do I back all 30 database at the same time?)
Then do a Restore from the SQL Server 2005 instanceIs this a good method or using the "Copy Database Wizard" is better method?
I have upgraded our test server and on non cluster production machine. My next server is a cluster and I don't have a test cluster server. Do I upgrade the active node and that is all or am I going to need to fail it over and upgrade the other node.
Also the prerequesite for the upgrade advisor is .net 2.0 I am going to up that on each server one at a time but I am only going to add the upgrade advisor to one node is that ok.
I read the SP1 documentation and it clearly states only patch the active node and do not patch the inactive nodes.
I used the SQL Server 2005 Upgrade Advisor to upgrade from SQL Server 2000 Enterprise to 2005 Standard. The only complaint I got concerned DTS packages, but I had none anyway. When I open SQL Server Management Studio, I can run queries, but they're against tables in the old 2000 databases. The SQL engine and Server agent are version version 8.0. Not surprising that new TSQL statements like 'BACKUP SERVICE MASTER KEY TO FILE' won't work.
Do I have to uninstall my previous version before upgrading?
I'm trying to upgrade the Default Instance of MSDE 2000 Release A which is installed with Mixed Mode and strong password to SQL Server 2005 Express in a Windows 2000 Server with SP4. On the Upgrade Logon Information screen, if I select SQL Server Authentication Mode, it will give me this message:
SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade.
I also migrated the server level logins using SSIS transfer logins task, available on SSIS 'Transfer logins', I selected all the databases that I have migrated so that I have all database users account in server logins (to avoid orphaned users); but I don't have all the database users in server logins, also the sys.sysusers doesn't have the database users, that I have moved to SQL 2005. Can anybody help?
Also do I need to back up the SQL Server 2000 database and restore it on SQL 2005? What impact this operation can have?
My database is running right now at SQL Server 2000 Enterprise Edition. We would like to upgrade it to SQL server 2005 Standard Edition.
Since this database was upgraded from MS Access 2000 to SQL server 2000. This database is accessed by a proprietary application. I don't know some of the details about this application.
There is one more issue with this database, replication was implemented earlier and now it is disabled.
I am thinking that to take a full backup from SQL server 2000 and restore it in SQL server 2005. What do you think?
Please let me know if you have any other idea.
I have another question for you. Right now replication is disabled and I restore SQL server 2000 database to SQL server 2005. Would there be any problem when we try to implement replication again?
Hi,I am new to the mysteries of SQLDMO.I have written a program whereby the user can select which SQL serverto connect to on the Network and this works fine.I am using the SQLDMO.Application.ListAvailableSQLServers routine andthis works fine.However, the Server on the users machine appears as 'Local'I need to display the server name as the actual server name instead of'Local'Any ideas how to do this with SQLDMO.I know I could delve into the registry and get the name from there, butI want to avoid this.CheersAlex
