Viewing 15 posts - 5,116 through 5,130 (of 59,089 total)
Heh... I'll give you another one... I interviewed a guy that claimed to be an expert at tuning SQL and T-SQL. I asked him what a clustered index was and...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 18, 2021 at 5:48 am
Heh... so a DBA doesn't need to know what a Clustered Index is???
Sorry... Unless you're trying to hire a TRUE SYSTEM ONLY DBA, I find that laughable and even a...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 18, 2021 at 5:31 am
Why? If what you're saying is true, then just use the first char in the value as the category, that's less overhead than any kind of table lookup.
Because...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 18, 2021 at 12:10 am
Here are a couple more that won't have a corresponding END.
- BEGIN CONVERSATION TIMER;
- BEGIN DIALOG CONVERSATION;
- BEGIN DISTRIBUTED TRANSACTION;
Just curious... have you actually ever used any of those?
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2021 at 11:13 pm
I have used that before.. but was looking for something that would dump tables in order with foreign key reference in mind, so I could pickup this file and...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2021 at 9:33 pm
If this is to be done on a Prod box, I wouldn't. If this is to be done on a Dev box, my question would be, why don't they already...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2021 at 9:18 pm
If you're using PIVOT, you should have posted the code anyway... there is a method that usually better than PIVOT.
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2021 at 9:10 pm
You claim to have 3rd party software that demonstrates that. Why do we need to provide an example? I've never seen such a thing but could be wrong. Post the...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2021 at 8:18 pm
According to your sample data and results, the "Answer" you marked is not correct. For example, you stated that '10000' should return a 1 -- "Anything between 00000...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2021 at 8:09 pm
Why? If what you're saying is true, then just use the first char in the value as the category, that's less overhead than any kind of table lookup.
Because...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2021 at 8:07 pm
I've found that it's not often a "slow running query" is the actual problem. I've found that it's normally one that could certainly run better/faster/fewer-resources that runs hundreds or thousands...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2021 at 8:05 pm
p.s. I also wouldn't use the "data" feature of the above method because it creates and INSERT/VALUEs statement for every bloody row of data.
If you use a product like RedGate...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2021 at 7:56 pm
If you only need to do this occasionally, it might just be simpler to open the Object Explorer window in SSMS (press the {f8} key to open it if it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2021 at 7:54 pm
Thank you for your inputs I apologize for my mistake in my sample the last case statement is 9. not 0.
Thank you for all your assistance and guidance
Ok... that...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2021 at 5:44 pm
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...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 17, 2021 at 5:03 pm
Viewing 15 posts - 5,116 through 5,130 (of 59,089 total)