Viewing 15 posts - 3,346 through 3,360 (of 3,475 total)
Reading Kimball's book on Data Warehousing isn't a bad place to start. It's a great introduction to the concepts in DW design and modeling. But it's definitely true...
July 22, 2013 at 9:46 am
I did it with a Matrix report.
Row: ProductDate
Column: PersonName
Intersection (value): ProductName
or did it have to be in query?
July 12, 2013 at 9:52 am
I think that will work. I knew I had to be making it waaay harder than it really was.
Thanks!
July 9, 2013 at 8:23 pm
omid.shokri (7/7/2013)
This query is the part of a procedure.
I think no different these two query, but output of query 1 is without any row. In other word, "Inner...
July 7, 2013 at 10:09 pm
Is this homework? When you ran it, did you notice any differences?
OUTER joins show all the records from the LEFT table, and matches or nulls in the right side...
July 7, 2013 at 4:14 pm
Could be me, but I think you're making this infinitely harder than it really needs to be. If you think in terms of SETS and use pure SQL, you...
July 3, 2013 at 6:43 pm
This worked for me... (FWIW)
insert into temp (id, strg, [index])
values (1, 'abc', 1);
declare @strg varchar (5)
select @strg = case when ID = 1 and [INDEX] = 1
then strg
else cast(0 AS...
June 24, 2013 at 2:58 pm
Actually, a point in time restore is probably the best option... I was thinking that the damage had not already been done - but if it has, that's your best...
June 2, 2013 at 9:41 pm
Yes, you could, but that's like killing a mosquito with a bazooka. Wrapping the statements in question in a transaction would be much less overhead and work.
June 2, 2013 at 4:16 pm
probably sp_sendDBMail and jobs. Definitely not triggers.
May 14, 2013 at 10:55 am
not much to go on...
what kind of message? Based on what? Service Broker might be a solution.
May 12, 2013 at 1:37 pm
I'm a recovering Access developer, so my opinions may help you (and may well not).
Anyway, Access is good for prototyping and front ends (if you cannot use ASP.NET or VB.NET...
May 7, 2013 at 5:10 pm
This design:
CREATE TABLE #TestTb1 ([Sample_ID] VARCHAR(10), [P1] INT, [P2] INT, [P3] INT, [P4] INT)
is going to bite you. I would strongly recommend not doing that. (I worked on...
May 4, 2013 at 9:40 pm
Wrong design.
CREATE TABLE Test(
PatientID int,
TestID int,
Reading decimal(10,4)
TestDate DateTime
);
Then the rest is trivial.
May 4, 2013 at 5:53 pm
Viewing 15 posts - 3,346 through 3,360 (of 3,475 total)