Viewing 15 posts - 26,446 through 26,460 (of 59,099 total)
Although it's not technically a backup of a single table, you could move the clustered index (which is really the table itself with a B-Tree in the rafters) and the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2013 at 10:53 pm
I've resigned myself to the fact that even the world's MVPs don't have much of an impact on what MS does. For example, there's been an "approved" CONNECT item...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2013 at 4:30 pm
I have both a full size tower on my work desktop and a work-provided laptop. I wouldn't have it any other way.
First, I never need to store anything important...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 14, 2013 at 3:36 pm
This would be a great place to use Table Partitioning which, after being built, would allow the nearly instantaneous "movement" of rows. It does take the "Enterprise Edition" to...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2013 at 5:16 pm
Easy guys. We're all in this together.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 12, 2013 at 4:03 pm
I guess I don't know the answer to your problem then. I was thinking that a full restore was takeing you 6 hours and, although a piecemeal restore bring...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2013 at 8:14 am
Do you know how long a full restore (non-piecemeal) of all filegroups takes?
Also, are the filegroups of the larger tables that you've partitioned "Read_Only"? If not and IIRC, all...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2013 at 6:32 am
Even though the explanation of exceeding the max INT value is completely wrong, I'm absolutely amazed that more than 1/3 of the people that answered this question got it wrong.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2013 at 6:22 am
RobertYoung (7/11/2013)
So, three different kinds of DBA, none compatible with the others.
I absolutely agree that's true in most cases. However, some of us do wear multiple hats as "Hybrid"...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 11, 2013 at 6:08 am
First, thanks a bunch for the updates on this. We're getting close to doing the same thing (update) and this will help with some of the things to watch...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2013 at 10:39 pm
ccmret (7/9/2013)
I am trying to get a EmpID where the PayID is not null. My problem is that an employee may have several EmpID’s.
Gosh... unless you have a DateActivated...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2013 at 10:27 pm
I suspect the fundamental skill of logically analyzing a problem and coming up with a set of steps to solve it is becoming more important all the time.
It sounds harsh,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2013 at 10:15 pm
Please post the link that you mentioned so others can see what you have seen. Thanks.
If you want to generate a million rows of sample data using those ratios,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2013 at 8:44 pm
Test Code...
DECLARE @BitBucket BIGINT
SET STATISTICS TIME,IO ON
SELECT TOP 1000000 @BitBucket=ROW_NUMBER() OVER (ORDER BY (SELECT NULL))
FROM sys.all_columns ac1, sys.all_columns ac2;
SELECT TOP 1000000 @BitBucket=ROW_NUMBER() OVER (ORDER BY (SELECT 0))
FROM sys.all_columns ac1, sys.all_columns...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2013 at 8:15 pm
It wasn't an article. It was a post on the Running Total article and Tom updated it with a slightly different take on the check. Tom's post with...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 9, 2013 at 7:49 pm
Viewing 15 posts - 26,446 through 26,460 (of 59,099 total)