As much fun as it is to be dumping and loading data in pursuit of application functionality, it should be within the capabilities - but perhaps "below the pay-grade" - of a developer dealing with a "complex banking system" to write a exportmenusettings.p and importmenusettings.p
"I'm convinced now that the best way forward for me is to just copy the files to the new servers using a task. I'll certainly pass on your feedback to our IT-guys for a more efficient way in the future!"
Upgrade the IT guys next.
If there is another payment solution already in place, it might be easier to extend it , rather than adding a-la-cart applepay and google wallet. Whoever is reconciling payments might thank you down the road.
Depending on number of records returned, hardware issues or lack thereof, buffer hit rates, other database activity and which runs first (for each vs open-query ), you might end up with the one that runs first, taking longer.
Save the dlc\properties\*.properties files and copy them to your new 9.1E instalation on server 201x or even better 2022 if you have new enough hardware to support it (ie TPM 2.0).
As for not being able to refer to printers by the UNC share name ... it can still work.
You might have to enable...
The workaround is to "copy" the file using the UNC name for the device.
OS-COPY filename \\machinename\printersharename (can be the same machine you are printing from or some oher machine on the same network).
PRN, LPT1, COM1 etc "access" has been limited since VISTA came out.
You are welcome :)
The most equivalnet to kill -9 on windows is taskkill /IM exenamehere /F ( taskkill /? to find out all the interesting ways to wreck havoc with it ).
Since this started happening at multiple sites, event logs on the client and the server should be looked at as well , to see what the OS is...
Not everyone is in a position to slam the brakes on a "change" before it happens.
Also you must appreciate the vagueness of hardware changes.
Why the drive was changed in the first place, what it was changed from , and most importantly if there was indeed "something" wrong with the drive who...
You may be preaching to the wrong choir. The sermon, amuzing at first, starts to get repetitevly annoying.
...and yet here we are. There is a chance among all the "buy my product or service" presentations over the years I might have missed the ones on how to implement "more secure" "security"...
Seeing all this information makes me want to know how all extents prior to .d21 are limited to 2GB .
Was enablelargefiles used before figuring out the reason for the sudden growth?
I love using 2GB extents for this specific reason :)
A database being used to store scanned documents will start increasing at an obscene rate for only two reasons:
A) A LOT and I mean really a lot more documents are being stored than before ,
or the more usual reason: A scanner or scanners were replaced and now the size of the scanned documents...