u/FranceRocks2

There is a legacy MS Access database that has a table needed for a query. Occasionally when accessing the table from SQL Server, the SQL Server instance just crashes. In other words, the SQL Server process is killed and noone can access sql server until it is restarted. Some of the information I have read say it is a known issue, and recommended using OPENQUERY as opposed to prefacing the database name with the linked server. That seems to work better, however even OPENQUERY crashes sql server sometimes. What seems to always best is if I manually in SQL Mgmt studio expand the linked server to display the tables. However we have an automatic process that needs to run without any manual intervention. Any suggestions for manual queries to 'prime' sql server so it does not crash when accessing that data?

I inherited a legacy application with a SQL Server backend. Some of the SQL is Microsoft-specific T-SQL. There is some concern about dependency on one database vendor, Microsoft, if the backend uses Microsoft-specific T-SQL which parts do, and the suggestion is to be database-agnostic. Are any shops worried about that? One idea raised was re-writing the backend code into ANSI SQL. Another idea was just to make the rule that future development should be ANSI-SQL compliant.

Is this a concern of others? If so, what are some options of database backends that people are using now, or suggestions on versions for people to test and verify their code runs against?

Thank you in advance!