Viewing 15 posts - 30,511 through 30,525 (of 59,101 total)
As a side bar, it's always amazed me that people find importance in the order of the data in a file without actually having something in the file to preserve...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2012 at 3:33 pm
Heh... a Rose, by any other name, is still a Rose.
Unless I'm mistaken, all of the examples above all boil down to some form of parent/child relationship.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2012 at 3:23 pm
gmcnitt (3/30/2012)
I think rollup is required, just can't seem to get it right. thanks!
Correct. Post the code where you tried WITH ROLLUP and let's see what we can figure...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2012 at 12:37 pm
MyDoggieJessie (3/30/2012)
You could try this, works pretty wellSELECTPin,
CDate,
btn,
callduration,
charge
FROM #gmreport
ORDER BY pin
COMPUTE SUM(callduration), SUM(charge) BY pin
Careful now... that's actually been deprecated not to mention that it will return multiple result...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2012 at 12:35 pm
Most likely its a parent/child relationship. I can't think of any other reason to do such a thing.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2012 at 12:32 pm
If there's something that uniquely identifies the rows (such as a PK or other candidate column), load the incremental data into a staging table, delete all the rows in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2012 at 12:30 pm
From Books Online...
Tail log backups capture the tail of the log [font="Arial Black"]even if the database is offline[/font], damaged, or missing data files. This might cause incomplete metadata from the...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2012 at 12:25 pm
kuppurajm (3/30/2012)
I have a table like
rowid CustLevel ...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2012 at 7:52 am
Phil Parkin (3/30/2012)
Jeff Moden (3/30/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2012 at 7:47 am
amy26 (3/29/2012)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2012 at 7:09 am
If you can make a small mod to your Calendar table... I usually create a Calendar table with 2 date columns to easily solve such an eventuality. The first...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2012 at 6:49 am
Ok... thanks. How would you like to have it parsed?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2012 at 6:43 am
vinaypugalia (3/30/2012)
Adding any User objects to the Master DB is a very BAD idea.
Heh... At the risk of starting World War III, you are denying yourself one amazing tool for...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2012 at 6:39 am
Jeff Moden (3/29/2012)
jeffrey.farr (3/29/2012)
Like I mentioned, it just parses the column/variable @TA and stores the data in another table.
Please post an example of what @TA would contain. If it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2012 at 6:25 am
I have a problem with using XML for such a thing simply because there's a comparatively large BYTE overhead thanks to all of the embedded tags. Of course, then...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2012 at 6:24 am
Viewing 15 posts - 30,511 through 30,525 (of 59,101 total)