I'll give this a try when I'm back in my office. The difficult we do right away... ...the impossible takes slightly longer.

Thanks, Richard! The difficult we do right away... ...the impossible takes slightly longer.

OriginalGriff wrote: Come on guys! If you have data which uniquely identifies a transaction and you are compiling a transaction report INCLUDE IT! If you have an "industry standard format" like Excel, use the modern version, not one 15 years out of date! Don't restrict the transaction count to an arbitrary number, restrict it to an arbitrary number or the end of a month / week / year whichever is appropriate! And whatever you do, don't add a further length limit to one particular format! I pointed all of that out to them. I suggested upgrades for years. I even wrote the tickets, added the designs, the breakdowns and estimates. But the architect and manager kept saying that no one actually uses that stuff and we really need more razzle dazzle for facebook. ------ I really have worked on multiple systems that would fail all the time because the original designer never even considered the possibility that a data dump might be too large at some point.

Wait, you tweaked the PRODUCTION server? CloudStrike is hiring. :) Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.

when you are fixing the msoledbsql issue, make sure the OLE DB provider matches your SQL Server version and that all necessary Visual C++ Redistributables are installed.

I don't see "on-premises" as a general option for a future disgruntled enterprise customer. I know that the binary choice of one vs the other is the current way of thinking. But actually, when you think about 'cloud' and 'local' in their limiting cases (ie, all cloud vs all local), then compare the two, you only really have somewhat of a case to go on-prem if you are a huge enterprise since the other limiting case is a single human being doing computing with himself, like playing cards on a PC. But even for large enterprises, detailed connections with the outside world are just as imperative as they are for a small business or even individuals doing anything on the computer. The above is true and will remain true, in my opinion, as long as the case for individual human beings doing computing remains impractical regarding establishing sets of durable end point to end point connections with the outside world. From this scenario the cloud is merely a kind of a superfluous man-in-the-middle. But that discussion is too far away from the OP's disaster shout-out.

Thanks, Richard. I'm frankly surprised that there's no documented way to return only specific result sets. I'll probably end up using the additional parameter to suppress output. Cheers. The difficult we do right away... ...the impossible takes slightly longer.

I got your point.

Doesn't say SQL-92 compliant, only that it has at least some features. " SQL-92 Compliance The SQL-92 standard is imprecise with regard to arithmetical operator precedence; assumptions on this matter differ amongst SQL implementations. Caché SQL supports two system-wide alternatives for SQL arithmetic operator precedence: By default, Caché SQL parses arithmetic expressions in strict left-to-right order, with no operator precedence. This is the same convention used in ObjectScript. Thus, 3+3*5=30. You can use parentheses to enforce the desired precedence. Thus, 3+(3*5)=18. You can configure Caché SQL to parse arithmetic expressions using ANSI precedence, which gives higher precedence to multiplication and division operators than addition, subtraction, and concatenation operators. Thus, 3+3*5=18. You can use parentheses to override this precedence, where desired. Thus, (3+3)*5=30. Caché SQL supports the complete entry-level SQL-92 standard with the following exceptions: There is no support for adding additional CHECK constraints to a table definition. The SERIALIZABLE isolation level is not supported. Delimited identifiers are not case-sensitive; the standard says that they should be case-sensitive. Within a subquery contained in a HAVING clause, one is supposed to be able to refer to aggregates which are “available” in that HAVING clause. This is not supported. " -- Introduction to Caché SQL | Using Caché SQL | Caché & Ensemble 2018.1.4 – 2018.1.9[^]

Downloads: Generic Database Access[^] This a HUGE Codeproject article which, from the looks of things (quick scroll through the .zip content), is likely to give out many C# programming secrets wrt SQL Server (even) with no further sacrifice of time searching on your part. Generic Database Access[^]

MarkTJohnson wrote: how long were you "puckered"? I would have been puckered if I had truly needed those backups. As it was, I went through a few emotions: 0: Surprise! Your false sense of security has just been shattered...You are not as clever as you thought you were, and your backups are shite! :omg: 1: Doubt...Hmmm what about the other 20 daily backups? Are they all shite? :confused: 2: Relief...Whew! The other backups are fine. Just these two from this server are crap. 3: Annoyance. I just want to get on with work. Now I have to log on Azure, allow myself to RDP into that box, get raw unzipped backups, and start troubleshooting the problem. 4: Sleuth Mode...the problem seems to be with the zip lib...maybe a bug...maybe fixed? Go get the latest version to find that it's being deprecated, and the last version is 6 y/o. Whatever, I'll try it. 5: Disappointment. :sigh: Nope that didn't work, time to open the project and debug with one of the dbs having the issues. 6: Excitement. :-D Yay! I was able to replicate the issue...now on to understanding. 7: Discovery: A well-phrased search put me on the right track...a known issue with an easy fix. 8: Humility: I'm sure I would have discovered this eventually, but I put a lot of faith in an automated process without actually verifying the outputs, which was the only way to detect the problem. Lesson learned! :laugh: "Go forth into the source" - Neal Morse "Hope is contagious"

Thank you so much Dear Ravi Bhavnani, You are truly amazing with very clear and comprehensive ideas, especially that you are not the person who discourages other, rather the person who encourages others to develop himself. I would liked to be in contact with you in private. As far as the analysis is concerned, I've already done the basics and I've also found that it's really a project that will solve several needs specifically in our local community. I'm then looking for the technology that can be best adapted to my project. Thanks again for your suggestions, guides and advice.

Hi Rene, I have no experience with kdb+, and I don't know if it works with your development tools. I went to a couple of live demonstrations of it a few years ago. There is a "Q" programming language that was similar to SQL, and less verbose. I can't remember if it was aggregation, but the speed was incredible. You might want investigate it: kdb+ | KX[^] Hope that helps. Quote: Richard Rogers LinkedIn: https://www.linkedin.com/in/rrcdn/

Gawd, is that the root reason? I've always been *so* against these third-party apps that try to sneak into Windows to replace default behavior. This is exactly why.

Thank you that was very helpful.

Again the point is that you are looking for a complete solution for something that contains multiple pieces. You must look for each piece then put them together.