Office Hours: Database Questions in Hong Kong
Вставка
- Опубліковано 5 тра 2024
- Today's Office Hours comes to you from the Hong Kong harbor. I went through your top-voted questions from pollgab.com/room/brento. Here's what we covered:
00:00 Start
01:18 Jason G - RN & Accidental DBA: Would you elaborate on DB Owner implications? sp_Blitz help recommends using the SA account, but the articles referenced by Andreas Wolter advocate for using low privileged accounts which are DB specific. Which would you recommend and why?
02:44 MyTeaGotCold: Can you name any good relational databases that aren't built around SQL? It's strange that a system so old is still the best.
03:58 John: Hello Brent. Is SQL Server 2022 ready for production/prime time and more more huge bugs/issues? Asking due to last blog post was in 2023 on that particular topic. Thanks.
04:57 Chicago Joe: Is there a trend to move database access to API only? I am asking because we are moving to next version of ERP and our CIO has told database developers that only access to new database will be through a Web API. Database is still on prem on next version, too.
06:23 J. Fisher: Hey Brent, Are you able to comment/explain SQL Server "Native" Geography/Geometry datatypes, other CLR stuff, and how they can use and exhaust "App Domain" memory... leading to "Unloading due to memory pressure"... Can't "afford" to keep adding memory.
08:19 Steve E: Hi Brent, Is there a way to assess overall reads per table across a workload in an attempt to see which tables we might want to focus our index tuning efforts to? Eg if the Posts table has 90% of the overall workload reads, we would probably want to start our index tuning there.
09:29 neil: dev thinks "azure" will solve all their problems. (they dont understand we're already sql on azure vm). they're committing all the same mistakes that created disasters on-prem. what surprises are they in for ?
11:12 Dream catcher: What time do you like to go-to bed and wake up? Do you nap after lunch?
11:43 ChompingBits: What do you think is nominally the difference between ADF and SSMS? ADF has query plans and access to many of the admin tools and reports in SSMS. How long do you think Microsoft will continue to offer both tools.
12:45 gringomalbec: Hi Brent, we realize you recommend not using Linked Servers to connect to other MS SQL Servers. But my friend asks if you find ok using Linked Servers to download data from sources other than MS SQL Server that cannot be connected directly in SSMS using Database Engine ? - Наука та технологія
Linked servers: "So You're Telling Me There's A Chance?"
🤣
I know you hate linked servers.. but what ab.. No.
What if they.. No.
But there are good tim..No.
Welcome to HK!! You nailed the weather!
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? 🤔
@@sirajudeenmuhammedibrahim6799 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 😆
@@HakanKindstromArnoldson 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...
@@HakanKindstromArnoldsonsounds 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!