Sql Server Errors
Moderators: chulett, rschirm, roy
Sql Server Errors
Can anyone tell me some common errors while loading from or to Sql Server.. Thanks..
The issues are the same for everyone with any database:
1. Dates not in the proper form for the stage (OCI or ODBC) connecting to the database
2. Data type mismatches because the ETL didn't properly check or transform the source data
3. Truncations to columns during loading because source data larger than target columns
4. Primary key violations during load because inserts and updates are not differentiated
5. Foreign key violations during load because foreign keys were not validated during transformation
6. Table/column names unknown because table definitions old/invalid/user-defined sql never tested
1. Dates not in the proper form for the stage (OCI or ODBC) connecting to the database
2. Data type mismatches because the ETL didn't properly check or transform the source data
3. Truncations to columns during loading because source data larger than target columns
4. Primary key violations during load because inserts and updates are not differentiated
5. Foreign key violations during load because foreign keys were not validated during transformation
6. Table/column names unknown because table definitions old/invalid/user-defined sql never tested
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Vinod
U also need to be aware of the stage u are going to use to load data into SQL server -DRS stage or ODBC enterprise stage.
There is a problem of memory leak with DRS stage and ODBC enterprise stage when u use data types of type timestamp and decimal. U will see this leak especially if u try to load large volumes of data and a large size of the data record.
One way to get around the decimal data type is to replace it with a double.
Here is an earlier link:
viewtopic.php?t=96316&highlight=odbc
Thanks
bmadhav
U also need to be aware of the stage u are going to use to load data into SQL server -DRS stage or ODBC enterprise stage.
There is a problem of memory leak with DRS stage and ODBC enterprise stage when u use data types of type timestamp and decimal. U will see this leak especially if u try to load large volumes of data and a large size of the data record.
One way to get around the decimal data type is to replace it with a double.
Here is an earlier link:
viewtopic.php?t=96316&highlight=odbc
Thanks
bmadhav
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: