Viewing 15 posts - 17,881 through 17,895 (of 59,069 total)
GSquared (4/11/2016)
If the business defines "closest in time" as what they want to match, then it's not wrong.
I have to disagree with that in a lot of cases. I...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2016 at 9:09 pm
GilaMonster (4/12/2016)
Jeff Moden (4/12/2016)
John Mitchell-245523 (4/12/2016)
...
FROM TableA, TableB
...
FROM TableA CROSS JOIN TableB
... as are these two:
...
FROM TableA, TableB
WHERE TableA.ID = TableB.ID
...
FROM...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2016 at 8:08 am
cad.delworth (4/12/2016)
John: you're a star, and thanks.
Clearly my SQL education has been so Prim and Proper that I have never ever been...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2016 at 8:07 am
John Mitchell-245523 (4/12/2016)
...
FROM TableA, TableB
...
FROM TableA CROSS JOIN TableB
... as are these two:
...
FROM TableA, TableB
WHERE TableA.ID = TableB.ID
...
FROM TableA INNER JOIN...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2016 at 7:55 am
Thank YOU for the feedback on what you're doing. It's great to have some insight as to the needs of others.
For what it's worth, I also sometimes run across...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 12, 2016 at 7:46 am
J Livingston SQL (4/11/2016)
if there are millions of rows as suggested then it would be good to see...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2016 at 4:12 pm
ttdeveloper (4/11/2016)
Thanks for this suggestion. I did consider using triggers across our databases but one reason has me worried about this.
Performance. Our design essentially will be querying...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2016 at 3:56 pm
Hugo Kornelis (4/10/2016)
SELECT List,...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 11, 2016 at 6:07 am
Ed Wagner (4/10/2016)
I have no experience with Asigra at all, but I'm a fan of using native SQL backups. That's what we use and they haven't failed me yet.
Ditto...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 10, 2016 at 2:30 pm
Heh... ok... I take it back. I was asked to troubleshoot some problems in some code I've never seen before and I now even hate XML used for configuration...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 10, 2016 at 2:15 pm
From the Article:
See Comments in the code for more details.
Awesome. I don't very often see such a useful bit of header information. You've provided a succinct yet accurate...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 10, 2016 at 8:32 am
xsevensinzx (4/9/2016)
jay81 (3/31/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2016 at 10:56 pm
I believe I'd be tempted to use a trigger to do inter-database referential integrity. Specifically, an "Instead of" trigger. From BOL...
[font="Arial Black"]DML Triggers[/font]
DML triggers are frequently used for...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2016 at 10:39 pm
ttdeveloper (4/8/2016)
Great suggestion on the UDF. To be honest i didnt think about that option. Ill give it a shot this morning and see what the outcome is....
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2016 at 10:30 pm
Lynn Pettis (3/29/2016)
Just seems a little cleaner:
with ConvertDate as (
select cast('01-' + string as date) DateValue
from (values('Dec-15'),('Jan-16'),('Feb-16')) test_data(string)
)
select datename(month, DateValue) + ' ' + datename(year, DateValue) MonthYear from ConvertDate;
I absolutely...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 9, 2016 at 10:01 pm
Viewing 15 posts - 17,881 through 17,895 (of 59,069 total)