Viewing 10 posts - 1 through 10 (of 10 total)
You can, actually; I spoke too soon (misinterpreted an error I received on FK creation).
May 19, 2009 at 8:03 am
Exactly, I just wish there was some way to enforce a FK constraint on a column serving as part of a composite PK (LocationID), though a check constraint might work...
Thanks...
May 19, 2009 at 7:36 am
It does make sense, but I'm going simpler still. I'm just throwing away both [PeriodStart] and [PeriodEnd] and DATEADDing the source [Date] timestamp (00:00:00.000) to the relevant hour.
I can't think...
May 18, 2009 at 3:32 pm
Ah, but normalization is what made me suggest Option #2... I'll keep reading 8)
May 18, 2009 at 3:21 pm
Hey G, thanks a lot for the reply.
Thinking about it from the perspective you related really makes sense: the only necessary predicates for this data are the date, the location,...
May 18, 2009 at 1:08 pm
Hey thanks for posting this! I've been dealing with the inconvenience of writing out the column names by hand for a long time now lol...
June 13, 2008 at 2:33 pm
Freakin' awesome article, man. I had no idea such things as these existed. I have seen the light. Thank you!
May 22, 2008 at 12:39 pm
Right on guys; thanks very much for the responses.
That was essentially the solution I used (running the CREATE PROCEDURE statement with EXEC).
February 28, 2008 at 9:54 am
For the record, according to BOL, there's just no way to directly combine CREATE PROCEDURE with any other T-SQL statement within a batch.
February 27, 2008 at 4:33 pm
Hey Sugesh,
Thanks for the reply.
I know dropping the procedure first works just fine. My essential question is this:
How do you create a stored procedure...
February 27, 2008 at 3:41 pm
Viewing 10 posts - 1 through 10 (of 10 total)