Viewing 15 posts - 8,101 through 8,115 (of 59,098 total)
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
Disclaimer: I don't use Ola's good code nor do I use "AG" (we use something else at work).
I understand that you currently have a single job but it would appear...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2019 at 3:35 pm
Just be careful not to over-provision the number of files in TempDB. The "standard" recommendation is 1 file per core up to 8 as a start and then tune from...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2019 at 3:21 pm
Odd question, have you contacted the CRM-provider about the slowness?
+1 Million for that suggestion.
Also, do you have a proc that properly maintains statistics and (to a lesser extent) fragmented...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 17, 2019 at 3:14 pm
Ummm... call Ola's stuff differently for specific databases?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 16, 2019 at 11:20 pm
Viewing 15 posts - 8,101 through 8,115 (of 59,098 total)