This is likely caused by an encoding mismatch between Synapse and SAS. I would start by checking the encoding of your SAS session. Please run this and post the results: proc options option = encoding; run; ... View more

In my experience ODS EXCEL is very resource intensive for large data volumes. I'd be tempted to forgo formatting and just use PROC EXPORT or the XLSX LIBNAME engine. as it will run a lot faster.  ... View more

In my experience most data centres only have shared server storage these days so it doesn't matter how you mount drives you will get the same performance.  ... View more

What OS was the SAS V6 catatog created under? It would have to be under the same OS you are now trying to read it. Also a V6 catalog is likely 32-bit. What bitness SAS are you trying to read it with?   You could try a test like this: libname mytest v6 '\MyV6folder'; proc catalog cat=mytest.MyCat; contents; run; quit; Please post the SAS log from this test. ... View more

@Ksharp - For those on old maintenance releases like SAS 9.4M1/M2 the EXCELXP tagset is still a better option as ODS EXCEL wasn't mature back then...🙂 ... View more

Not sure if this is any help to you but here are some examples of OLE DB connection strings up to SQL Server version 2019. These can be used as is using the LIBNAME NOPROMPT option.   Also have you tried something like this: libname MyOLEDB oledb noprompt="Provider=MSOLEDBSQL19; Server=MyServer; Database=MyDatabase; UID=MyUsername; PWD=MyPassword; Use Encryption for Data=Optional; Trust Server Certificate=True;"; The connection string in your CONNECT statement should work unchanged in your LIBNAME statement. ... View more

Is ODBC an option? We use SAS/ACCESS Interface to ODBC with SQL Server a lot and haven't had any problems upgrading to newer database or database driver versions at all. ... View more

Your single dataset update step may look similar to this: In this example the step took a real time of 0.01 seconds. Set FILELOCKWAIT to a value in seconds greater than the real time of your update step.    ... View more

Yes this is easily doable and I do this myself a lot. If there is only one permanent SAS library affected then add the FILELOCKWAIT option to your  LIBNAME statement like so:   libname MyLibRef 'MyFolderPath' FILELOCKWAIT = 30; The value you assign to FILELOCKWAIT is the number of seconds you want SAS to wait if someone else is currently updating any dataset in that library. It should be greater than the number of seconds it takes to update your shared dataset.   ... View more

I had a quick look at that website but see no mention of Tuva being open to third-party products like SAS. It looks like you are limited to Tuva-supplied interfaces. There is mention of a Tuva user community so I'd suggest asking about third-party access there for a more definitive answer. ... View more

Server backups are the usual way to protect against deletion. In my organisation I simply request a restore of the deleted files. That way you are protected regardless of how files are deleted or corrupted. ... View more

What happens if you just run your old working code with the driver updated: LIBNAME MyLibrary OLEDB PROMPT=NO DATASOURCE=MyServer PROVIDER='MSOLEDBSQL19' SCHEMA=dbo USER=MyUsername PASSWORD=MyPassword; ... View more

Looks like the ODBC driver can't handle exponential notation. That is a perfectly acceptable number if you assign it in SAS. I suspect you will have to cast the column into a format acceptable to the ODBC driver, but the first thing would be to identify which one is causing the problem. Try selecting a subset of the columns until you identify it. Also what external database are you reading?   ... View more

Please post your complete SAS log so we can see what the code and errors are.  ... View more

EG 8 doesn't appear to allow having multiple projects open at the same time unfortunately. A workaround would be to open multiple EG instances and open different projects in each.  ... View more