N problems encountered when porting MySQL database to SQL server

The following articles mainly describe some problems encountered during the migration of MySQL databases to SQL server. The reason why MySQL databases to SQL server can be widely used in a short period of time is as follows, this is also because of its unique features. The following article describes the specific content.

TABLENAME:

LOG: System. IndexOutOfRangeException: Column1

In System. Data. ProviderBase. FieldNameLookup. GetOrdinal (String fieldName)

In System. Data. SqlClient. SqlDataReader. GetOrdinal (String name)

In System. Data. SqlClient. SqlDataReader. get_Item (String name)

In Pixysoft. Framework. Noebe. NoebeCommand. ExecuteReader ()

Note: An unhandled exception occurs during the execution of the current Web request. Check the stack trace information for details about the error and the source of the error in the code.

Exception details: System. Exception: TABLENAME:

LOG: System. IndexOutOfRangeException: Column1

In System. Data. ProviderBase. FieldNameLookup. GetOrdinal (String fieldName)

In System. Data. SqlClient. SqlDataReader. GetOrdinal (String name)

In System. Data. SqlClient. SqlDataReader. get_Item (String name)

In Pixysoft. Framework. Noebe. NoebeCommand. ExecuteReader ()

This is mainly because my SQL is SELECT COUNT (*) FROM TABLENAME.

No column is specified, so DbDataReader reader = command. ExecuteReader (); no column name = "" is returned in the returned data.

My code is through the reader component table, so that datacolumn is faulty. When this occurs, it is out of the border. The above content is an introduction to the problems encountered when the MySQL database is migrated to the SQL server.

The above content is an introduction to the problems encountered when the MySQL database is migrated to the SQL server.