Viewing 15 posts - 6,841 through 6,855 (of 59,091 total)
Is there more than one "Address" element per XML or is there always just 1 (regardless of how many attributes that node contains)?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2020 at 6:00 pm
Only the temporal tables. So one would be customer and another would be customer address. The report would show the transactions against each chronologically for example
Username, EventDate, Table, NewValue,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2020 at 5:50 pm
Lordy, Joe. The OP didn't design any of this. It's cut'n'paste from homework or a test.
Also, the stuff about the "1960s pointer chains is not relational"... that's a load of...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2020 at 5:29 pm
This is either homework or a test of some kind. At least TRY to do something on your own, post it, and if you have a question you can't answer...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2020 at 3:38 pm
Heh... getting a little older and being prone to affib has changed what I call my "best day". My "best day" is always TODAY. It means that I woke up...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2020 at 3:24 pm
I am working an exercise problem where the solution provided has a WHERE clause used in a way I have not seen before. The question asks, "to show the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2020 at 2:40 pm
I agree with the notion of a view that dkultasev posted. If these types of changes are infrequent, then manually building one would be fine. If these tables change a...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2020 at 1:59 pm
It would be helpful if you posted the CREATE TABLE statement for the table both before and after each change you make to the table. Also, the devil's in the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2020 at 1:53 pm
It would be real helpful if you were to describe what you mean by "it does not work". What isn't it doing and what, if any, are the error messages?
Also,...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2020 at 1:30 pm
See the 2nd link in my signature line below on the information you should provide on performance related problems. Thanks.
Okay thanks I'll follow this guideline going forward. Could...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 4, 2020 at 2:00 am
Developers think its always DBA's fault bcz the query is running slow . Initially they were pulling data to temp tables which we corrected into physical tables and drop...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 3, 2020 at 12:15 am
See the 2nd link in my signature line below on the information you should provide on performance related problems. Thanks.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 2, 2020 at 5:04 pm
Our developers are running a huge select query pulling millions of records for a datawarehouse and when examined the query shown no issues in the Executionplan .
Heh... you've correctly...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 2, 2020 at 4:58 pm
@as1981 ,
Apologies for missing your question on this.
Yes, it's possible to work it out from historical information as you've said but it's still pretty much of a SWAG simply because...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 1, 2020 at 7:47 pm
I don't know if it will help in this case but you CAN write a unique index with an "Ignore Duplicates" attribute that will simply not insert duplicates and won't...
--Jeff Moden
Change is inevitable... Change for the better is not.
June 30, 2020 at 8:49 pm
Viewing 15 posts - 6,841 through 6,855 (of 59,091 total)