Viewing 15 posts - 3,811 through 3,825 (of 22,213 total)
May 18, 2017 at 11:23 am
May 18, 2017 at 11:15 am
Following Microsoft's ELT, as opposed to ETL, approach to Data Warehouse, you sure should be able to make that work. I'd offer to test it for you, but I'm a...
May 18, 2017 at 6:28 am
Ha! I don't. Have you tried using a tally table and Jeff's queries? I haven't tested that, but it'd be my go-to.
May 17, 2017 at 11:07 am
For the load process, bump it up to a premium service tier so you have more memory and faster processing, then bump it back down when the load is done.
May 17, 2017 at 11:06 am
Have you patched your Management Studio. I'm using the 2017 version now, but I just wrote an IF script nested 10 layers deep and it's not affecting anything and I...
May 17, 2017 at 7:54 am
Thanks Grant. Am I understanding you right here - even though I am only...
May 17, 2017 at 5:53 am
May 17, 2017 at 5:49 am
May 16, 2017 at 4:10 pm
May 16, 2017 at 4:02 pm
SSIS is the slowest way to move data into Azure SQL Data Warehouse. The fastest way is using flat files and polybase to read the files into tables. It's quite...
May 16, 2017 at 12:12 pm
A full text index might help. They're mainly meant for searching within books, that sort of thing, not so much a short varchar field. You could test it to find...
May 16, 2017 at 11:54 am
Since you have a search like that, it can't possibly use any indexes, so adding one is unlikely to speed things up. At least one resulting factor is that a...
May 16, 2017 at 10:55 am
Also, it's not the IF statements that are likely causing it to slow down, it's all the additional queries validating values. EXISTS is a good way to short circuit the...
May 16, 2017 at 10:52 am
May 16, 2017 at 10:46 am
Viewing 15 posts - 3,811 through 3,825 (of 22,213 total)