David Yard

The GA for the Azure SQL Database free offer is here! Learn, develop, or do a POC on Azure SQL for the lifetime of your subscription for now up to 10 databases. techcommunity.microsoft.com/blog/azuresqlb…. aka.ms/freedboffer #azuresql

Great day at beginners guide to data integration with Cathrine #PASSDataSummit

Today I asked the developer did you know you removed the no lock and now we have 10+ deadlocks a day. Response was deadlocks are the preferred method. What’s your comments on that? #sqlhelp

Attending pre con Sql Saturday La-SQL Server Performance Tuning with Free Tools by John Sterrett- Great Info

@jdanton @SqlrUs Thanks Joey

@SqlrUs @SQLYard At 5 TB, the only good solution, IMO, is log shipping/AG to a VM, and then something else within Azure if you have bandwidth.

I’m currently researching how to sync data on prem to azure . Would azure sync be a good candidate? 5TB db. #sqlhelp

@SqlrUs Migrate the data from on prem to azure data lake

@SQLYard Can you clarify what you mean by Azure Sync? Do you mean File Sync? Data Sync? and to which service offering in Azure? DB? MI? VMs? #sqlhelp

@AngryPets Thanks for the help

@SQLYard This is likely pretty close to your issue: learn.microsoft.com/en-us/archive/… That's obviously a bit older - but you're running into throttling at 1 or more compilation gateways (small, medium, large). COULD be due to insufficient RAM, eager-plan-clipping, or a combination. 1/..

SQL error logged filled with this today sev17 time out occurred while waiting to optimize the query #sqlhelp anyone experience this?looks about 50 minutes until ended

@AngryPets Error 8628 that’s it for about 34 minutes thanks

@SQLYard Without more specifics (i.e., exact error numbers/etc.) ... sounds like a problem with RESOURCE_SEMAPHORE_QUERY_COMPILE. Which is a problem with a) too much code complexity and b) too many concurrent requests for complex, compiled, plans. #sqlhelp Can you post some Error #s?

@PASSDataSummit Thank you it was a great week

And just like that, it is time we say our goodbyes! THANK YOU ALL 🙌 for an amazing #PASSDataCommunitySummit! We leave with fulfilled 💕 and 🧠 knowing our community grew strong and long-lasting connections were shaped. 👀 See you again in 2023!

@bobwardms @PASSDataSummit Great session

Back to my roots today at the @PASSDataSummit talking Debugging SQL Server. windbg, AVs, hangs, spinlocks, assembly. #SQLServer #debugger #OldSchool #sqlhistory.

@MidnightDBA I’m interested

Oh yeah, if y'all want to join our SQL Server Discord server, let me know! I'll send you the link. #sqlfamily

Attending #PASSDataCommunitySummit

#sqlhelp Looking for some suggestions, are network is trying to replace are native backup a solution with Rubrik. Looking for pros and cons if any one has any, thanks

@jdanton Thanks for the help, we will rebuild that node, we have system dbs on d drive #sqlhelp

@SQLYard Not at all, it’s an official MS recommendation *for* TempDB. Not master, model, and msdb. #sqlhelp

Anyone know using Alwayson in azure with azure node if issues using the D drive when failing over? should D Drive not be used? #sqlhelp

@jdanton ok thanks, are network told us having the system DB on the d drive is causing the failover process not to work as expected. I was trying to find some documents on this. #sqlhelp

@SQLYard You should only ever use the D (ephemeral) volume for TempDB. It’s fine to use that in an AG. Don’t use it for user databases. #sqlhelp

#SQLHELP Has anyone had this error. I have a case open with Microsoft one month now still waiting ,The Database Engine received a floating point exception from the operating system while processing a user request. SQL 2016 and 2019