Viewing 15 posts - 5,626 through 5,640 (of 59,101 total)
Sending the same message to the WebMaster does the trick, Kristen. I've made the same mistake in the past and, especially because you're able to identify the post, they can...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2021 at 2:11 pm
If you reread what I wrote, you would see that I don't agree with creating a view for future proofing.
I stated that using a view for refactoring is acceptable...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2021 at 4:42 am
There are a whole lot of things that SHOULDN'T be done to a table. The fact the matter is, they DO happen in real life, Jeffrey, and you have to...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2021 at 2:29 am
I would like to compare two files, that should give me. a Match and No Match output in separite tables. Can somebody send ma screenshot/link of such a ssis...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2021 at 2:14 am
Thank you for the response. I am using unique bar codes in both files. I want the result to split in two, match and no match OlE DBs.
When...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 21, 2021 at 1:56 am
@JeffModen - your solution and my solution are very close to the same. If we pass in 2022 as the starting year - both version return an empty...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2021 at 7:49 pm
What is the criteria for your Match/NoMatch condition?
For example... are you looking for matches by whole line in the files? If not, how do you need to differentiate which parts...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2021 at 4:48 pm
Ah, be careful, now... There actually IS a problem with making a view for every table... if you make a change to the table, you need to remember to "refresh"...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2021 at 4:33 pm
In the absence of any code, the one thing that might have helped me to help you was the Predicate listing. So much for that, eh? 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2021 at 2:13 am
It might be the default but doesn't apply in this situation.
0 = varchar(max), nvarchar(max), varbinary(max), xml and large UDT values are stored directly in the data row, up to a limit of 8000 bytes...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 20, 2021 at 1:53 am
@JeffModen - your solution and my solution are very close to the same. If we pass in 2022 as the starting year - both version return an empty set. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2021 at 9:58 pm
WITH
E1(N) AS (SELECT 1 FROM (VALUES (1),(1),(1),(1),(1),(1),(1),(1),(1),(1))E0(N))
I don't understand this syntax (please note that I'm not a DBA - my day job...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2021 at 4:20 pm
Thanks for the feedback but my question was how do I autoupdate the decommisioned column using a query or some script that says the server is decommisioned ? My...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2021 at 4:00 pm
Thank you so much everyone for your interesting, thoughtful and useful answers and contributions. I didn't 'leave the building' but I'm in the UK and after work stops, I...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2021 at 3:36 pm
I have an actual TALLY table in my database for Numbers ... is that bad? should I be using a Function?
Obviously there is a limit on the number of...
--Jeff Moden
Change is inevitable... Change for the better is not.
February 19, 2021 at 3:29 pm
Viewing 15 posts - 5,626 through 5,640 (of 59,101 total)