Viewing 15 posts - 24,856 through 24,870 (of 59,102 total)
ELLEN-610393 (1/6/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2014 at 1:56 pm
Yes... rename each table and build a synonym for each table using the original table name. Build an additional table for each table and populate it with the "current"...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2014 at 1:00 pm
jeandlauro (1/6/2014)
I just mean I thought it would be easier to link Microsoft data tools together.
I've been wondering the same thing for years (almost 2 decades, now). When I've...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2014 at 12:56 pm
Sridhar-137443 (1/6/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2014 at 12:48 pm
Hugo Kornelis (12/9/2013)
marcia.j.wilson (12/9/2013)
Any examples of how these would be used?
Running totals. Traditionally done with slow set-based code, with a (relatively!) fast cursor, or with some dangerous unsupported side effect...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2014 at 12:11 pm
ChrisM@Work (1/6/2014)
Does your table have an assocoation with...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2014 at 9:16 am
Better yet, stop storing denormalized data in the form of XML in your database (never mind storing it twice!). 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2014 at 9:11 am
elham_azizi_62 (1/6/2014)
ALTER procedure [dbo].[icanSP_Convert_GetEntityDependencies]
@DocId INT,@Count int
as
begin
;WITH MyTable AS (
SELECT * FROM (select linknumber,savabegh from main2 where savabegh is not null and...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2014 at 9:07 am
First, thanks for the test. On the subject of defending MS for the slowness of FORMAT based on the fact that it's a generic function, I'm sure that it...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 6, 2014 at 1:18 am
born2achieve (1/5/2014)
First of all i don't have enough vocabulary to thank you because the way you answering to the forum questions are much professional and elaborated which will help...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2014 at 8:22 pm
Ok, here we go. It always takes me a little longer than others because I like to explain things a bit.
First, I like Michael's code the best out what...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2014 at 4:39 pm
born2achieve (1/5/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2014 at 2:47 pm
Almost forgot. What do you want to do about the Jul 2013 to Jul 2014 scenario that I previously stated?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2014 at 1:02 pm
born2achieve (1/5/2014)
Thanks for your precious time on this post and here is my exact business requirement,
From the sample i have provided, assume current date is January 5th which...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2014 at 12:59 pm
The Many-to-Many table doesn't mean that this isn't in 3rd Normal form.
For the "conflict" resolution that you seek, you're going to need to setup some sort of a "rules" table...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 5, 2014 at 12:14 pm
Viewing 15 posts - 24,856 through 24,870 (of 59,102 total)