Viewing 15 posts - 1 through 15 (of 122 total)
Just to refer to the orginal problem:
The root problem of the big log file could be fixed / prevented, if you would partition your tables. Ola's script would in this...
May 9, 2022 at 12:46 pm
when you are working with dynamic SQL and particularly, when it uses varchar-parameters and adds it to the dynamic code, you have always to use QUOTENAME(), otherwise someone could call...
November 29, 2021 at 9:26 am
@hmbacon: you could either do 6 Updates each joining the base table or - if the select of the base table is slow / difficult - write the...
October 20, 2021 at 9:24 am
The DELETE WHERE id IN (SELECT TOP x) is still a very bad solution. You wrote that it makes a table scan in your first example, so I assume that...
October 15, 2021 at 9:26 am
@dave_rogers: I disagree with your "rule". It is often much easier to query a log table (even if it will be never joined to whatever) than to read / search...
October 8, 2021 at 11:47 am
ok, theoretical you could for the cursor "problem" declare an additional variable, increase it inside the loop and write a WHILE @i < 999999999 instead of 1=1
But what, if someone...
September 22, 2021 at 4:03 pm
Did you just click onto the link and tried it out? It is only a simple database / table on a webserver and a web frontend where you could enter...
August 6, 2021 at 3:29 pm
Nice, but it would be nicer, if I could also search for
...
August 6, 2021 at 12:35 pm
@jeff - but both it is linked together 🙂
@Jeffrey: of course I'd cluster your table by PatientID, DocID too. But when you are not a very new hospital...
June 17, 2021 at 8:24 am
Stupid question, but why are some people use a low fill factor as 70 or 80%, I'm usually fine with something as 95-98 (or even 100 if it is on...
June 16, 2021 at 1:06 pm
Nice article, but I think it could need a second follow up article
May 21, 2021 at 2:07 pm
I manage a big DWH database (about 12 TB). Of course (for this size) the database is partitioned. The biggest tables have their own set of annual filegroups (e.g. FG_ORDERS_2019,...
February 23, 2021 at 10:30 am
we are saying, that #1 and #3 are correct, not #3 and #4.
LEAD with descending order is the same as LAG with ascending order (except that the returned rows are...
February 16, 2021 at 4:10 pm
@scott: The question, if they should cluster for it or not depends, how else this table is used. Yes, 2,400 deletes per day may be a lot, but...
February 9, 2021 at 8:41 am
regarding the clustered index recommentation:
you do not necessary have to cluster your table by MyTime. When MyTime is ascending too (e.g. the creation timestamp) you may e.g. simply selecting the...
February 8, 2021 at 4:17 pm
Viewing 15 posts - 1 through 15 (of 122 total)