Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
swoozie
Starting Member
25 Posts |
 Posted - 2013-11-05 : 12:20:18
|
| Please move if this is in the wrong forum. I have been searching for this answer and I am not locating it. I keep finding resumes with it on it instead which makes me believe that I am not using the right terminology.I have been in SQL for years, but I am back out in the job market and I am finding that alot has changed or expanded. I am looking for a reference or source to explain the handing of Dirty Records.I understand dirty records, and queryin, and handling them, but I am at a lost on "Create a Table to save Dirty Records"It seems like this should be simple, but them I wonder why you want to save dirty records? There must be a resource I can read on this topic.Please assist. |
|
|
James K
Master Smack Fu Yak Hacker
3873 Posts |
Posted - 2013-11-05 : 12:43:10
|
| Where did you see this quote? "Create a Table to save Dirty Records" ?In SQL Server terminology, dirty records refer to records that have been modified but have not yet been committed. That means that if you were to read dirty records, there is a possibility that the transaction that caused those records to be changed could be rolled back and hence the data you read would be incorrect. Is that what you meant when you said you understand dirty records?If that indeed is the case, I am not familiar with any recommendation or document that suggests one should save dirty records. |
 |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2013-11-05 : 12:54:00
|
| My guess this has something to do with ETL type processing. And may be by dirty records they meant invalid records due to some data quality/integrity issues. We usually have a step where in ETL tools like SSIS we'll have a path to process these error rows and save it in table/file and notify the source authority on it to make correction and resend as a new version. But again we refer them as invalid/error records and not dirty records.------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/https://www.facebook.com/VmBlogs |
|
|
|
swoozie
Starting Member
25 Posts |
Posted - 2013-11-05 : 14:07:31
|
| I am guess now after I have read and read, that the "Dirty Records" being refered to are not the uncommitted transactions, but the invalid records from an ETL that visakh16 mentioned. Would have been easier to just say invalid records. That term I am familiar with. I create an "Exceptions" table to the business rules we have created for the data processing.Anyone else want to chime in on what they think this means? |
|
|
|
|
|
|
Dirty Records