Viewing 15 posts - 7,891 through 7,905 (of 59,091 total)
We're getting a bit lost here because I wasn't clear my last post. I'm thinking this isn't the only query that will be played against the column.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 16, 2020 at 7:20 pm
Given that the table had no index at all, I didn't think in this case that making the clus index unique was necessary, particularly to the extent of adding...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 16, 2020 at 4:24 pm
That being said, I'd love to see the schema of the table and what the real use of finding the max date would be for this table.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 16, 2020 at 4:15 pm
Adding to Lynn's post, I will say that having a UNIQUE Clustered Index is usually better because it gets used in all Non-Clustered indexes, as well.
To wit, I do have...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 16, 2020 at 3:38 pm
Sorry, I am curious as to how it can do this and what factors influence it; I would like to know when indexes are needed for these types of...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2020 at 8:51 pm
What are you suggesting by lesser environment?
This...
We don't have any testing machine provided yet. I doubt we will get it though.
That's a very real problem. There should be...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2020 at 7:04 pm
Hi,
We have an OLAP cube built with 2016 version. Now DBA team is planning to migrate to 2019 SQL server version. This is a general question that if there...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2020 at 5:43 pm
Yeah, I see where the paranoia comes from. However, I can also see how the NSA would prefer a more secure Windows OS.
Heh... the first thought that came to...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2020 at 3:08 pm
Jeff Moden wrote:(heh... no one uses column store, right? :D) but didn't say so. My bad.
BWA-HA-HA!!!
Exactly.
I sure wasn't trying to correct your answer, just add to it.
Not to worry. It's...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2020 at 3:03 pm
With regard to the recovery model, I'd forgotten about Bulk-Logged. It's definitely something to consider. Another part of the standardisation is to review the backup policies and procedures so...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2020 at 2:14 pm
I have my production databases set to be "exposed" to the possibility of a transaction log backup every 15 minutes, but it's stupid to do an actual T-Log...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2020 at 2:08 pm
Jeff Moden wrote:p.s. And stop using REORGANIZE for your index maintenance.
With the noted exception of columnstore indexes, but only when working in 2016 SP1 or greater.
Correct. Thanks for the...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2020 at 1:58 pm
I try to avoid to have hit the table for each section of code and then try to avoid more than 1 section of code. With a little help from...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2020 at 4:55 am
Lately, the migration assistant also transmits a shedload of information about the servers involved to Microsoft, which I don't believe I want them to have no matter how benign they...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2020 at 1:38 am
The problem in step 4 is that you actually have 2 transactions in step 3 but have only committed once. In step 3, you run it once with COMMIT commented...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 15, 2020 at 1:34 am
Viewing 15 posts - 7,891 through 7,905 (of 59,091 total)