Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with etl
Search options answers only
not deleted
user 61
'Extract, Transform and Load': Data load processing, normally in the context of data warehouse systems.
3
votes
SQL join on col1 if present else use col2
The problem here is that using a function or or around your join predicate means that the database engine can not use any indexes that you might have defined on the relevant columns for seeking so it …
- 32.4k
3
votes
Is it faster to truncate destination and copy all source data or lookup and keep only non-ma...
processing by SSIS if your ETL is more complicated than "read from here, write to there" - i.e. are you seeing a lot of CPU and/or IO activity from SSIS? …
- 32.4k
1
vote
Accepted
Truncate and insert: Heap and build index or directly into Clustered table
I would keep the clustered index in-place especially if the data is being inserted in large lumps (rather than lots of individual inserts).
You should drop the non-clustered indexes if rebuilding the …
- 32.4k
3
votes
Huge Size (still) with Differential Backup
Depending on the complexity of your ETL process refactoring it this way may be a massive job. … Depending on your data sources and the complexity of the ETL process you may have better luck with building the warehouse DB at both locations each time, as Chris suggested in the comments. …
- 32.4k