Viewing 15 posts - 30,676 through 30,690 (of 59,101 total)
Example: Table ProductSummary
Columns: Date, Product, Vendor, Total
Rule: One row per day at maximum.
So, one row per date per product per vendor, correct?
And you want running totals by day and not...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2012 at 6:00 pm
I guess my suggestion would be to dump the CLR altogether and do the data layer calculations in the data layer.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2012 at 5:47 pm
wendy elizabeth (3/14/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2012 at 5:42 pm
codebyo (3/20/2012)
Jeff Moden (3/20/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2012 at 5:26 pm
codebyo (3/20/2012)
SQLKnowItAll (3/20/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2012 at 4:53 pm
SQLKnowItAll (3/20/2012)
ColdCoffee (3/20/2012)
I dont see a triangular join here. Its pretty straight forward join. Or maybe im overlooking something here :blink:Triangular join because the join condition is >=
Also, look at...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2012 at 4:45 pm
GSquared (3/20/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2012 at 4:37 pm
michael wang-201906 (3/20/2012)
thank you everyone, i will try to create...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2012 at 10:24 am
mahesh.shiv (3/20/2012)
I would like to know about this book 'MS SQL Server 2008 Professional Programming' by Robert Vieira .
Considering the way this thread has been going, let me first say,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2012 at 10:22 am
Just a tip. The two jears worth of employee data probably shouldn't be in separate tables to begin with. Understanding that it may not be possible to actually...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2012 at 9:22 am
michael wang-201906 (3/20/2012)
i met a very wierd problem this morning. i have a SSIS package, which clean a table, then run a SP to insert records to this table....
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2012 at 9:14 am
Eugene Bereznuk (3/20/2012)
I have to BCP this table "out" and then "in" to another table (which, normally, is faster than INSERT..SELECT..).
If the target table can be dropped before being...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2012 at 7:00 am
I personally never use PIVOT because I don't like it the way they wrote it (PIVOT in Access is much easier and more more powerful) and it's comparatively slow.
The following...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2012 at 6:53 am
The following two articles will teach you how to handle just about any situation. For character based columns, use MAX instead of SUM.
http://www.sqlservercentral.com/articles/T-SQL/63681/
http://www.sqlservercentral.com/articles/T-SQL/63681/
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2012 at 6:47 am
Thought I'd throw my own version of sp_SpaceUsed out there. Undoubtably, this will need to be updated some time in the near future but it works just fine in...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 20, 2012 at 6:44 am
Viewing 15 posts - 30,676 through 30,690 (of 59,101 total)