Viewing 15 posts - 21,691 through 21,705 (of 59,072 total)
First, thank you for taking the time to build the test data. That will really help.
It would be helpful if, instead of trying to figure out what the overall...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2015 at 10:30 am
kd11 (1/25/2015)
ManagerName EmployeeName HoursWork
John...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2015 at 10:13 am
You bet and thank you for the great questions and feedback throughout this thread. Let us know how it all works out when you get the chance.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 25, 2015 at 9:39 am
k.allen.emt (1/24/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 24, 2015 at 9:29 pm
Crud. Almost forgot... I know it sounds a little weird but, even though the shrink will make a fragmented train wreck out of the database, consider doing the reindexes...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 24, 2015 at 9:18 pm
Once you shrink the database, as pietlinden says, you'll need to rebuild all indexes. Despite how good many of the index routines written by various people are, a lot...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 24, 2015 at 9:14 pm
Nah. Done correctly, audit triggers are fast and a breeze to write. It also depends a bit on whether you're doing "whole row" auditing or "column level" auditing,...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 24, 2015 at 8:54 pm
I've never worked with Azure but, according to the following article...
https://msdn.microsoft.com/en-us/library/azure/hh508997.aspx
... it looks like you'll need to recombine the individual tables to take advantage of partitioning and you should absolutely...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 24, 2015 at 8:39 pm
sm_iransoftware (1/24/2015)
we are on emergency state.
Application is very slow and some times give time out.
in Database , which thing Should I examin in first step?
and then :...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 24, 2015 at 5:06 pm
Rahuul (1/24/2015)
We are in the middle of re-designing few tables (namely transaction tables) that would store very large data and would be hosted on cloud (Azure). The old design of...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 24, 2015 at 4:03 pm
Steve Jones - SSC Editor (1/24/2015)
Comments posted to this topic are about the item <A HREF="/articles/Editorial/121702/">Which Problem Are You Solving?</A>
Since 90% of any effective solution is the correct identification of...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 24, 2015 at 3:35 pm
I agree. It's like Developers and DBAs. I don't know why people treat them separately. They should be on the same team with the same goals. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 24, 2015 at 3:14 pm
Bunny786 (1/22/2015)
SQL Server not Shutting down or not crashing ,We have 15-20 developers to access the 30 TB database,Some of the developers are able to connect...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 24, 2015 at 3:09 pm
Correct. Inserts never go into the audit table. Only the changes from UPDATEs and DELETEs. If a row is Inserted into the Employee table, and is never...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 24, 2015 at 2:53 pm
Eric M Russell (1/24/2015)
I am thankful for introduction of the short Date and have made heavy use of it last few years.
Yes. I agree with that 100%. But...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 24, 2015 at 10:57 am
Viewing 15 posts - 21,691 through 21,705 (of 59,072 total)