Does it mean the beginning of a nightmare when program developers start to abandon technology? It is really difficult to solve the customer's simple problem after abandoning SQL Server 2000.

This topic originated from a report problem faced by a customer today. Report statements written using stored procedures run on SQL Server 2000. The customer said that there was a mistake, but I could not find an SQL Server 2000 on the machine side, all of which were SQL Server 2005/2008 R2. The customer's problem is that it is a default sorting rule.

 
Create Table# Bom (bom_no nvarchar (50) start_date datetime)Create Table# Part (bom_no nvarchar (50) part_name nvarchar (50) part_no nvarchar (50 ))SelectPart_name, bom_noFrom# Bom A, # Part BWhereA. bom_no = B. bom_no
 

There are two temporary tables, item list and item list details. Because no sorting rules are used during creation, the sorting rules are abnormal when the following read Statement is executed.

The problem is not complicated, but because the database SQL Server 2000 cannot be found, I am afraid to rashly send the SQL stored procedure that I think is correct, so I have to go over it, some are really not worth it.

First, go back to the company to find the installation of SQL Server 2000Program, Cannot be found, so search on the Internet, find it, download it, during installation, because there is a default instance for installing SQL Server 2005, change to the name instance for installing SQL Server 2000, after the installation is successful, enter sql2k \ Dev in system management. The program reports an error. The reason is that the SQL connection string we wrote is as follows:

Server = sql2k \ dev; database = northwind; uid = sa; Pwd = holiday;

In system management, it reads data once with sqlconnectionbuilder and extracts the datasource, that is, sql2k \ Dev. This is a named instance of SQL Server, not a network machine name, the system program uses the ping command to ping the sql2k \ Dev. Naturally, the ping fails.

CodeAs shown below:

 
BoolAvailable =False; Sqlconnectionstringbuilder conection =NewSqlconnectionstringbuilder (connectionstring );StringMachinename = conection. datasource; ping =NewPing (); pingreply reply = ping. Send (machinename, 4000 );
 

If the ping command fails, an exception is reported first, although the following connection string is correct.

In this way, you have to uninstall SQL Server 2005, reinstall SQL Server 2000, and change it to the default instance. The SQL connection problem has been solved.

 

Another problem is that we are using SQL Server 2005 for development. On the Development Department side, all ERP databases are SQL Server 2005 and there is no SQL Server 2000 database, which is troublesome, I know that SQL Server has the Import and Export function, but the SQL Server 2005 of the local machine has been uninstalled by me, so I have to append the database of the original SQL Server 2005 on another machine, export to my local SQL Server 2000. There are always some problems with SQL Server Import and export. For example, identity problems, primary key loss, and so on.

The demo databases of the Development Department are all in SQL Server 2005, which is a big headache. Even so, the problem has not been solved, so we have to ask the customer for the SQL Server 2000 database, ask the customer for the database for approval, and filter out sensitive prices and supplier data, several gigabytes of data are also very time-consuming.

In this way, nothing is done in a day, and a day is wasted.

 

SQL Server has an incompatible issue. Databases of higher versions cannot be opened in lower versions, even if you have the following settings

Even if your compatibility level is SQL Server 2000, the current database cannot be opened in SQL Server 2000. It only represents compatibility with SQL syntax.

Similarly, SQL Server 2005 databases cannot be opened in SQL Server 2008.

The SQL Server 2000 query analyzer can connect to the database instance of SQL Server 2005, but cannot execute any update statements, prompting that the version is not enough. This problem has been improved in SQL Server 2005. 2005 management studio can connect to SQL Server 2008 and execute the modification statement.

 

It is also the SQL Server database engine. SQL Server 2000 is good enough, and a large number of customers are using this version of SQL Server. Therefore, when selecting your SQL Server database, I thought it would be much better to start from a lower version. New customers we certainly require customers to select SQL Server 2005, but old customers, technicians, even bosses, are not able to persuade customers to upgrade to SQL Server 2005, this is an unnecessary waste of costs. From the perspective of our developers, most of SQL Server 2005 is used as its database engine, and other functions are hardly used. It is easy to use, and management studio is powerful. Therefore, we use SQL Server 2005 or even the updated SQL Server 2008.

 

I hope this will help you.