Viewing 15 posts - 616 through 630 (of 1,353 total)
Still no reason to go to a cursor.
I only use(d) a cursor to initially populate the dates. The susquent updates, including the holidays (each holiday date individually typed out),...
June 5, 2015 at 1:00 pm
Why would the day being a holiday be a problem?
It's not a problem, it's just that there's no date function for that and unlike almost all the others has to...
June 5, 2015 at 12:27 pm
Why do you need the hour? Is that necessary to populate the date when it's just the date? I'm intrigued by this method, but not sure it addresses...
June 5, 2015 at 11:27 am
None of the links worked for me. What am I not doing correctly?
June 5, 2015 at 9:21 am
Populating a date dimension can be done using a tally table. No loop necessary.
The code executes faster but it is also a LOT simpler to write than a loop.
The loop...
June 5, 2015 at 9:13 am
cursors are there to be used for admin scripts to be executed manually
I like this caveat, especially as it now excuses my one use I have for looping in TSQL:...
June 5, 2015 at 6:53 am
Creating a procedure to automatically rebuild or reorder indexes throughout your entire database is one.
Great example if you are going to do something other than simply reindexing the entire database....
June 1, 2015 at 8:22 am
And let's also consider the other reality--just because *you* may think you're a sql God--chances are the person maintaining that in 6 months won't be
For as much as I know...
June 1, 2015 at 7:44 am
Sometimes we use CURSORS in our order processing environment to move data between systems and changing statuses on each record processed. The main reason for using a cursor is that...
June 1, 2015 at 7:05 am
I have never read the statement "do not use cursors" in any other way than interpreting it as "do not use row-by-row operations, use set operations instead".
Agreed. Some...
June 1, 2015 at 6:57 am
Oh... and I almost forgot (this one is a brilliant). They have some funky "automated" way of creating their DWs but it means that most dimensions are basically cookie cutter...
May 14, 2015 at 6:48 am
The case/jury analogy was just to promote discussion in a situation where the contract is silent on certain issues (all contracts are silent on at least some things).
If they wrote...
May 14, 2015 at 6:47 am
Users could make use of other methods to query the underlying database
In other places, perhaps, but I don't allow that.
May 13, 2015 at 9:00 am
Not sure that I agree 100% with that statement Ron. If you incrementally load dimensions and then facts, this scenario (facts pointing to incorrect/non-existent dimension members) will not happen.
I'm...
May 13, 2015 at 8:43 am
that we should have explicitly specified that these errors (where the facts and dims get out of sync AND queried, during refresh) not occur
Yes, that's what I'm saying. Even...
May 13, 2015 at 8:01 am
Viewing 15 posts - 616 through 630 (of 1,353 total)