Often the case with ERP systems is that the major vendors are moving to the cloud and direct database access through customer developed enhancements cannot be tolerated in a shared cloud infrastructure. Epicor Kinetic ERP is a prime example. They are blocking use of key .Net libraries that provide direct database or filesystem access.
That's absolutely true, and I empathize with the ERP vendors there. They don't want customers going anywhere near direct database access, and they need to log (and prevent some) queries being run.
For SSMS, MSFT SSMS team has updated that there are no plans to stop updating it. They are investing in it. It was mentioned in an article having it documented with the SSMS 20 GA release page. For SQL Server 2022, yes, your point about Azure is still unresolved. Yes MSFT did highlight it as a major milestone for this release. Other than this, if we are still in OnPrem and starting to build with a new Cluster using 2022, do you have any recommendations?
@@BrentOzarUnlimited I mean, we are not in to Cloud business but in OnPrem still. In this case, SQL 2022 is the next version for our new Clusters. What other choice would you proceed as a next version? 🤔
Linked server, YES. The main reason to use a linked server would be to move data between servers internally like from a TEST or DEV server to a QA server for data migration so you don't have to create a SSIS package just to do that. The data moves much faster that way. 😁
Nope. Restore the most recent production backup onto those other servers and avoid all of the overhead of querying production. I ain't playin'.
9 місяців тому
@@BrentOzarUnlimited How would you stage a on-prem datawarehouse without linked servers? The only tool I have to connect with is a database and daily automatic backup restore seems is a terrible option. They error handling is limited in t-sql and they come out corrupt and get stuck in restoring. I would love to run our OLAP nonsense on the beefy app sql-server, but most DBAs aren't that stupid 😆
@@BrentOzarUnlimited That is an unusable mess for anyone born 2 year later then me or so ... and staging the data, (even if you index the stage properly) is usually not a significant part of the ETL load. But if the SSIS connection manager is more efficient then "other SQL server"-linked server. That would be interesting ... why wouldn't they just connect the same way SSIS does? It is already there...
Linked servers: "So You're Telling Me There's A Chance?"
🤣
Welcome to HK!! You nailed the weather!
I know you hate linked servers.. but what ab.. No.
What if they.. No.
But there are good tim..No.
The Harbour!! Thanks for posting Brent!!
Often the case with ERP systems is that the major vendors are moving to the cloud and direct database access through customer developed enhancements cannot be tolerated in a shared cloud infrastructure. Epicor Kinetic ERP is a prime example. They are blocking use of key .Net libraries that provide direct database or filesystem access.
That's absolutely true, and I empathize with the ERP vendors there. They don't want customers going anywhere near direct database access, and they need to log (and prevent some) queries being run.
For SSMS, MSFT SSMS team has updated that there are no plans to stop updating it. They are investing in it. It was mentioned in an article having it documented with the SSMS 20 GA release page.
For SQL Server 2022, yes, your point about Azure is still unresolved. Yes MSFT did highlight it as a major milestone for this release. Other than this, if we are still in OnPrem and starting to build with a new Cluster using 2022, do you have any recommendations?
"Other than it not being ready 2 years later, should we use it?" C'mon, bud.
@@BrentOzarUnlimited I mean, we are not in to Cloud business but in OnPrem still. In this case, SQL 2022 is the next version for our new Clusters. What other choice would you proceed as a next version? 🤔
@@smibrahim84 SQL Server 2019.
Linked server, YES. The main reason to use a linked server would be to move data between servers internally like from a TEST or DEV server to a QA server for data migration so you don't have to create a SSIS package just to do that. The data moves much faster that way. 😁
Nope. Restore the most recent production backup onto those other servers and avoid all of the overhead of querying production. I ain't playin'.
@@BrentOzarUnlimited How would you stage a on-prem datawarehouse without linked servers? The only tool I have to connect with is a database and daily automatic backup restore seems is a terrible option. They error handling is limited in t-sql and they come out corrupt and get stuck in restoring. I would love to run our OLAP nonsense on the beefy app sql-server, but most DBAs aren't that stupid 😆
@ SQL Server Integration Services.
@@BrentOzarUnlimited That is an unusable mess for anyone born 2 year later then me or so ... and staging the data, (even if you index the stage properly) is usually not a significant part of the ETL load.
But if the SSIS connection manager is more efficient then "other SQL server"-linked server. That would be interesting ... why wouldn't they just connect the same way SSIS does? It is already there...
@sounds like you’re not really open to other solutions, so I’ll let you go about your day. Good luck on your work. Cheers!
Yves Saint Laurent ʕ•͡-•ʔ.
Indeed!