Viewing 15 posts - 24,481 through 24,495 (of 59,102 total)
I wouldn't do this part in SSIS. Post some readily consumable data according to the first link in my signature line below under "Helpful Links" and if I don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2014 at 8:22 am
wak_no1 (2/5/2014)
It's proving to be a lot more complex than I first thought, for the sake of one missing...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 5, 2014 at 8:13 am
Sanjeev Jha-475652 (2/4/2014)
Thank you very much. This worked like a charm !
You're welcome. Thanks for the feedback.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2014 at 10:37 pm
dhananjay.nagarkar (2/4/2014)
I'm trying to do-If the "[Latest Filled Date]" equals the previous weeks Monday - Saturday dates...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2014 at 10:02 pm
For those that still work in 2005 that would like to play with such a thing, I've reworked the sample data to work in 2005 and up. This will...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2014 at 9:11 pm
Luis Cazares (2/4/2014)
SELECT
SUM(CASE qtr WHEN 1 THEN sales END) AS q1,
SUM(CASE qtr WHEN 2 THEN sales END) AS...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2014 at 8:48 pm
p.avinash689 (2/4/2014)
I'm using Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (Intel X86) Apr 2 2010 15:53:02 Copyright (c) Microsoft Corporation Developer...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2014 at 5:01 pm
Correct on all counts. The last bit of code you posted would be correct to make the query SARGable.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2014 at 4:37 pm
Ahhh.... I found the problem. It has to do with which trace file is selected and I've got it working on my prod server. I'm redacting the code...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2014 at 8:28 am
SQLRNNR (2/3/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2014 at 7:31 am
RexHelios (2/3/2014)
CREATE TABLE dbo.Employee (
EmployeeIDINTNOT NULL,
EmpFirstNameVARCHAR (50)NOT NULL,
EmpMiddleNameVARCHAR (50)NOT NULL,
EmpLastNameVARCHAR (50)NOT NULL,
EmpDOBDATETIMENOT NULL,
EmpSSNVARCHAR(11)NULL,
DateCreatedDateTimeNOT NULL,
DateModifiedDateTimeNOT NULL
)
I also have an audit table to keep track of changes made...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2014 at 8:45 pm
For such a small table as the given Employee table, I agree. If not CDC, then use full row auditing instead.
However, for very wide tables, this method is...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2014 at 5:39 pm
Grant Fritchey (2/3/2014)
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2014 at 5:16 pm
L' Eomot Inversé (2/3/2014)
Oh, if only the reasonably competent used it it would be great
BWAA-HAAA!!!! Absolutely agreed. I said the very same thing when SQLCLR, the XML datatype,...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2014 at 2:03 pm
To add to that, unless you only have a 100 customers or so, I think it a bit insane to return all customers at any time.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 3, 2014 at 12:06 pm
Viewing 15 posts - 24,481 through 24,495 (of 59,102 total)