Viewing 15 posts - 7,441 through 7,455 (of 59,072 total)
If I read this correctly - it seems you are saying that index maintenance needs to be based on that system. And based upon the data access patterns and...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2020 at 5:30 pm
thanks guys - I forgot about the number of VLF - one would expect that these days where this is well known fact that any DBA has already set...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2020 at 3:11 pm
I'm thinking that Type 6 SCD's may be better. With that, the use of Temporal Tables may be just what the doctor ordered here with the understanding that they won't...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2020 at 2:41 pm
I agree. Because there is no requirement for maintaining the order in which the parsed elements appear, String_Split() is the better choice here.
The thing is that you have to be...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2020 at 2:33 pm
I actually ignored her but that, in itself, is a large part of the problem.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2020 at 12:53 pm
BWAAA-HAAAA-HAAAA! Are you suggesting that I shouldn't tell the DA teen that selfied herself licking the toilet seat on an airliner to suggest that Covid-19 wasn't a big deal that...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 28, 2020 at 7:32 am
For reindexing, the "standard" advice floating around is still to reindex based on logical fragmentation percent.
For a variety of reasons we can get into if necessary, I don't think...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2020 at 8:58 pm
Please post the script if you want an accurate answer. Otherwise, my suggestion would be to read the following article.
If you actually have SQL Server 2017 or better instead of...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2020 at 8:22 pm
Speaking of hashes, you could create a hash column for all the columns and make that the Clustered PK. That would certainly be within the limits of a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2020 at 3:02 pm
Joe... I'm still waiting for you to identify the ISO Standard by number for what you're talking about that clearly identifies that the YYYY-MM-DD format is the only supported format...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2020 at 2:23 pm
Speaking of hashes, you could create a hash column for all the columns and make that the Clustered PK. That would certainly be within the limits of a CI.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2020 at 2:20 pm
Please... especially when posting a shedload of code, either learn how to post the code in a code window or attach it all as a txt file. When constructing a...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2020 at 2:14 pm
That sounds REALLY interesting, i have never been the type of person and i didn't knew you could make these kind of changes inside the engine if not using...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2020 at 1:55 pm
Instead of waiting for you, Joe, I found ISO/IEC 9075-1, ISO/IEC 9075-2, ISO/IEC TR 19075-2, (all 3 are part of ISO SQL standard) and revisited the ISO 8601 spec.
ISO/IEC 9075-1...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 27, 2020 at 12:49 am
>> You know that YYYY-MM-DD is the alternate format and it doesn't work in certain languages in SQL Server. You also know that the primary ISO format is YYYYMMDD....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 26, 2020 at 10:14 pm
Viewing 15 posts - 7,441 through 7,455 (of 59,072 total)