| bio | website | |
|---|---|---|
| location | Denver, CO | |
| age | 37 | |
| visits | member for | 2 years |
| seen | yesterday | |
| stats | profile views | 179 |
Developing, modeling, administering, tuning, troubleshooting, extracting, transforming, and loading databases full time since 1996.
First professional assignment with databases began building CAClipper xBase applications back when a database with 2 million plus records was considered huge. Moved to FoxPro and Borland Visual Delphi in the mid 90's and then SQL Server in '98.
Have also worked with Sybase, MySQL, Oracle, Access, Multivalue Informix, Filemaker, 4D and the Microsoft BI stack.
|
Mar 7 |
revised |
Change Data Capture and the __$update_mask binary added 3 characters in body |
|
Mar 7 |
revised |
Change Data Capture and the __$update_mask binary added 107 characters in body |
|
Mar 7 |
revised |
Change Data Capture and the __$update_mask binary added 258 characters in body |
|
Mar 6 |
accepted | TSQL DateTime DataType - fractional seconds vs milliseconds |
|
Mar 6 |
comment |
TSQL DateTime DataType - fractional seconds vs milliseconds Its turning out to be a "taking their word for it" problem on my end with the vendor proc. They are using the LSN time mapping functions related to change data capture which DO allow < instead of =< calls. So, we'll be fixing code. msdn.microsoft.com/en-us/library/bb500137.aspx |
|
Mar 6 |
comment |
TSQL DateTime DataType - fractional seconds vs milliseconds If the range was in our own code that would be what we would do but we are passing to other procs that only take datetime for range and are inclusive on both ends |
|
Mar 6 |
asked | TSQL DateTime DataType - fractional seconds vs milliseconds |
|
Mar 6 |
revised |
Capturing datetime of change in SQL Server CDC changed data type of approach from datetime to datetime2 |
|
Mar 5 |
revised |
Change Data Capture and the __$update_mask binary added 24 characters in body |
|
Mar 5 |
revised |
Change Data Capture and the __$update_mask binary added 93 characters in body |
|
Mar 5 |
revised |
Change Data Capture and the __$update_mask binary added 1 characters in body |
|
Mar 5 |
revised |
Change Data Capture and the __$update_mask binary added 229 characters in body |
|
Mar 5 |
revised |
Change Data Capture and the __$update_mask binary added 134 characters in body |
|
Mar 5 |
revised |
Change Data Capture and the __$update_mask binary deleted 237 characters in body |
|
Mar 5 |
answered | Change Data Capture and the __$update_mask binary |
|
Mar 5 |
asked | Change Data Capture and the __$update_mask binary |
|
Feb 18 |
revised |
Quick way to validate two tables against each other added 636 characters in body |
|
Feb 18 |
revised |
Quick way to validate two tables against each other edited body |
|
Feb 18 |
revised |
Quick way to validate two tables against each other added 2391 characters in body |
|
Feb 11 |
comment |
Quick way to validate two tables against each other Nice, thanks... good way to find differences after aggregate indicates differences exist. Thanks. |