Viewing 15 posts - 11,056 through 11,070 (of 59,099 total)
--Jeff Moden
Change is inevitable... Change for the better is not.
October 5, 2018 at 8:19 am
This should be a function but the either the OP or the OP's DBA Team thinks they should be avoided because of some "Best Practice" someone found somewhere stating that...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 5, 2018 at 8:10 am
I have a requirement wherein there are 2 tables (Staging & Target) in the same...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 5, 2018 at 7:57 am
in file have around 100000 records but command was successful with 0 records....
--Jeff Moden
Change is inevitable... Change for the better is not.
October 5, 2018 at 7:48 am
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2018 at 10:29 pm
Unless the rows are insanely wide, a 200,000 row insert is pretty much a cake walk for your initial insert. And, it can be done using "Minimal Logging", which not...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2018 at 10:09 pm
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2018 at 9:49 pm
We have no idea what you're table looks like, what indexes are available, nor any idea what the report is supposed to do/look like. A bit more of a description...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2018 at 9:43 pm
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2018 at 9:38 pm
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2018 at 9:18 pm
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2018 at 9:13 pm
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2018 at 7:37 pm
I guess I don't understand the desire to partition by two columns, never mind the PeriodYTD column. It would appear that the PERIOD column is based on month ending dates...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2018 at 7:03 pm
REBUILDs remove free space below the Fill Factor and create free space above...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2018 at 4:42 pm
It does exactly what it says so it's not a document error. It "compact{s}... based on the existing fill factor value". The documentation also clearly states that REORGANIZE will NOT...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 4, 2018 at 3:38 pm
Viewing 15 posts - 11,056 through 11,070 (of 59,099 total)