meta user
network profile
| bio | website | |
|---|---|---|
| location | Arkansas | |
| age | 32 | |
| visits | member for | 1 year, 5 months |
| seen | yesterday | |
| stats | profile views | 21 |
Data Warehouse Specialist / Database Developer / Database Administrator
|
Dec 14 |
answered | How does SQL Server determine the order it takes locks in while selecting a table? |
|
Dec 2 |
comment |
SQL Server Optimization/Configuration for Inflexible Application +1 Great answer Mark! |
|
Dec 2 |
comment |
Any security related reasons to prefer Windows Authentication over Sql Server Authentication? +1 Cut and dry. Additionally, kerberos delegation is only possible with windows authentication. I've seen enough linked servers set up to use the sa account that I appreciate the security added with kerberos delegation. |
|
Dec 2 |
answered | Loading a FACT table per day |
|
Dec 2 |
comment |
Failing SQL Job +1 Anytime the tran log is filling up, you either have to find a way to minimally log (sqlmag.com/article/tsql3/minimally-logged-inserts) or split the processing up into manageable chunks. You can use the advanced destination manager in ssis to seamlessly split the batch up, but this is still part of the manageable chunks arguement. |
|
Dec 2 |
awarded | Supporter |
|
Jul 9 |
comment |
Why "Select * into targettable from sourcetable “ is faster than “insert into targettable select * from sourcetable Very thorough answer JNK. Also, when implemented correctly and the recovery model is not full, a simple SSIS data flow task can be faster than either of these. Why? Both of the above will issue an exclusive lock (Read is multi-thread but write is single thread). As long as a table lock is used with the destination adapter, SSIS will use a bulk update lock (Both read and write are multi-thread). |
