Viewing 15 posts - 8,071 through 8,085 (of 59,072 total)
well the PK alone doesn't indicate real world duplicates as in you can create an index column of sorts but that doesn't solve potential duplicates and even where there...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2019 at 11:16 pm
Why do you need to do this? Any table with a unique index on it, even a non-clustered one, will not have duplicates in it. Same goes for any table...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2019 at 7:50 pm
Look in the upper right corner of the display for "Write for us". Click and follow your nose.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2019 at 7:43 pm
Duplicate post. Please... no posts here. No need to split up possible answers. Go to the first one in process at https://www.sqlservercentral.com/forums/topic/audit-failed-successful-login-log-4#post-3709164
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2019 at 4:02 pm
Duplicate post. Please... no posts here. No need to split up possible answers. Go to the first one in process at https://www.sqlservercentral.com/forums/topic/audit-failed-successful-login-log-4#post-3709164
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2019 at 4:02 pm
Duplicate post. Please... no posts here. No need to split up possible answers. Go to the first one in process at https://www.sqlservercentral.com/forums/topic/audit-failed-successful-login-log-4#post-3709164
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2019 at 4:00 pm
I've not worked with Dynamics... is that one of those MS applications/databases that uses random GUIDs for keys?
Yes!
With database designs that would make Codd break down weeping. They...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2019 at 3:39 pm
I've not worked with Dynamics... is that one of those MS applications/databases that uses random GUIDs for keys?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2019 at 2:39 pm
In mean time i have found solution.
Tnx guys
BR
Two way street here... what solution did you come up with?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 19, 2019 at 2:36 pm
In that case, use a non-clustered index on the hashkey. It will be more narrow than a clustered index and will run much more quickly.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2019 at 9:37 pm
Wonderful solution! Congratulations!
Hmmm... wait for it...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2019 at 9:32 pm
Hmmm... maybe an "Instead-of" trigger to reject DELETEs?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2019 at 9:28 pm
An alternative solution
;WITH cte AS
(
SELECT s.Teams, s.Category, SUM(s.Sales) Sales
FROM dbo.Sales s
...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2019 at 9:26 pm
I agree with Jeff Williams... contact the vendor for this information but be careful and don't hold your breath. They either won't have it or will be loath to part...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 18, 2019 at 9:20 pm
I a m developer (SSAS/SSIS) and familiar with the concepts of clusted and nonclustered indexes.
How much more about indexing/statistics/... should i have knowledge of?
What is "nice to have" and...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2019 at 4:15 pm
Viewing 15 posts - 8,071 through 8,085 (of 59,072 total)