PNG
IHDR
PNG IHDR
Skip to main content
💡 Day 10 of 365 – SQL Server Authentication Modes Security starts with authentication. SQL Server supports two main modes: 🔹 Windows Authentication Uses Active Directory accounts Centralized password management Strong security with Kerberos Recommended for production environments 🔹 SQL Server Authentication Uses SQL logins with usernames and passwords Independent of Windows accounts Useful for legacy applications or cross-platform connections 💡 Tip: Always prefer Windows Authentication when possible. If SQL Authentication is required, enforce strong passwords and expiration policies. Fellow DBAs: Which authentication mode do you mostly use in production, and why? #SQLServer #SQLDBA #DatabaseAdministrator #Security #AzureSQL #DBATips
💡 Day 9 of 365 – SQL Server Error Logs: Your First Troubleshooting Tool As a SQL Server DBA, the error logs are your first line of defense when troubleshooting issues. They contain valuable information about: 🔹 Service startup and shutdown events 🔹 Backup and restore operations 🔹 Job failures (via SQL Server Agent) 🔹 Hardware or connectivity errors 🔹 Security and login failures 💡 Tip: Use the built-in function to read error logs quickly: EXEC xp_readerrorlog 0, 1, N'error'; This lets you filter and identify critical errors efficiently. Pro DBAs always check the error logs before running scripts—it can save hours of troubleshooting. 👉 Quick question for DBAs: Do you archive error logs regularly in your environment? #SQLServer #SQLDBA #DatabaseAdministrator #Troubleshooting #AzureSQL #DBATips
To view or add a comment, sign in
💡 Day 9 of 365 – SQL Server Error Logs: Your First Troubleshooting Tool As a SQL Server DBA, the error logs are your first line of defense when troubleshooting issues. They contain valuable information about: 🔹 Service startup and shutdown events 🔹 Backup and restore operations 🔹 Job failures (via SQL Server Agent) 🔹 Hardware or connectivity errors 🔹 Security and login failures 💡 Tip: Use the built-in function to read error logs quickly: EXEC xp_readerrorlog 0, 1, N'error'; This lets you filter and identify critical errors efficiently. Pro DBAs always check the error logs before running scripts—it can save hours of troubleshooting. 👉 Quick question for DBAs: Do you archive error logs regularly in your environment? #SQLServer #SQLDBA #DatabaseAdministrator #Troubleshooting #AzureSQL #DBATips
To view or add a comment, sign in
🚨 SQL Server Service Failed After Server Rename & IP Swap - Resolved Recently, I worked on a migration activity involving: 🔁 Server rename 🌐 IP swap ⬆️ Upgrade from Windows Server 2016 → 2022 ⬆️ Upgrade from SQL Server 2016 → 2022 🔍 Situation: Old and new servers swapped hostnames and IPs New SQL Server 2022 instance inherited the old server identity As per compliance, the MSA (Managed Service Account) also needed to be updated accordingly ⚠️ Issue: While attempting to change the SQL Server service account to the new MSA: ❌ SQL Server service was NOT starting ❌ Unable to apply/change the MSA account ❌ WMI errors during configuration Errors observed: WMI Provider Error (0x8007042b / 0x80092004) Service terminated unexpectedly 🧠 Root Cause: SQL Server was configured with an SSL certificate, but: 👉 The MSA account did NOT have permission to access the certificate’s private key This caused: SQL Server service startup failure WMI configuration failures Account change not getting applied ✅ Resolution: Opened certlm.msc (Local Computer Certificates) Navigated to: Personal → Certificates Identified the bound SSL certificate Granted READ access to the MSA account on the certificate private key Restarted SQL Server service Re-applied the MSA account successfully 🚀 Result: ✔ SQL Server service started successfully ✔ MSA account updated as per compliance ✔ Migration completed without further issues 💡 Key Learnings: • Service account changes can break SQL startup if SSL is configured • Certificate private key access is critical for SQL Server • WMI errors can often point to deeper security/permission issues • Always check ERRORLOG before assuming configuration issues #SQLServer #DBA #DatabaseAdministration #MSA #WindowsServer #Troubleshooting #Migration #LearningInPublic
To view or add a comment, sign in
Master your SQL Server backups with a clear understanding of RTO and RPO. Tips for IT Managers: https://lnkd.in/gU6g_uPZ #BackupBestPractices #itmanager https://lnkd.in/gU6g_uPZ
PNG IHDR
To view or add a comment, sign in
Master your SQL Server backups with a clear understanding of RTO and RPO. Tips for IT Managers: https://lnkd.in/gU6g_uPZ #BackupBestPractices #itmanager https://lnkd.in/gU6g_uPZ
PNG IHDR
To view or add a comment, sign in
𝐎𝐫𝐚𝐜𝐥𝐞 𝐃𝐁𝐀 𝐅𝐢𝐫𝐬𝐭 𝐑𝐞𝐬𝐩𝐨𝐧𝐬𝐞: 𝐁𝐚𝐬𝐢𝐜 𝐃𝐚𝐭𝐚𝐛𝐚𝐬𝐞 𝐇𝐞𝐚𝐥𝐭𝐡 𝐂𝐡𝐞𝐜𝐤𝐬 Whenever an application team reports a database connectivity issue, the first responsibility of a DBA is to quickly verify the database health. Here are the basic checks every Oracle DBA should perform first 𝟭) 𝗖𝗵𝗲𝗰𝗸 𝗣𝗠𝗢𝗡 𝗣𝗿𝗼𝗰𝗲𝘀𝘀 The first check is whether the PMON background process is running. 𝑝𝑠 -𝑒𝑓 | 𝑔𝑟𝑒𝑝 𝑝𝑚𝑜𝑛 If PMON is not visible, the database instance is likely down. 𝟮) 𝗖𝗵𝗲𝗰𝗸 𝗗𝗮𝘁𝗮𝗯𝗮𝘀𝗲 𝗢𝗽𝗲𝗻 𝗠𝗼𝗱𝗲 Login to SQL*Plus and verify the database status: 𝑠𝑒𝑙𝑒𝑐𝑡 𝑜𝑝𝑒𝑛_𝑚𝑜𝑑𝑒 𝑓𝑟𝑜𝑚 𝑣$𝑑𝑎𝑡𝑎𝑏𝑎𝑠𝑒; For transactional applications, it should normally be: 👉 𝙍𝙀𝘼𝘿 𝙒𝙍𝙄𝙏𝙀 If it shows READ ONLY, confirm whether it is intentional. 𝟯) 𝗖𝗵𝗲𝗰𝗸 𝗜𝗻𝘀𝘁𝗮𝗻𝗰𝗲 𝗦𝘁𝗮𝘁𝘂𝘀 𝑠𝑒𝑙𝑒𝑐𝑡 𝑠𝑡𝑎𝑡𝑢𝑠 𝑓𝑟𝑜𝑚 𝑣$𝑖𝑛𝑠𝑡𝑎𝑛𝑐𝑒; The status should be: 👉 𝙊𝙋𝙀𝙉 This confirms the instance is up and accessible. 𝟰) 𝗠𝗼𝗻𝗶𝘁𝗼𝗿 𝗔𝗹𝗲𝗿𝘁 𝗟𝗼𝗴 Always keep an eye on the alert log for real-time issues: 𝑡𝑎𝑖𝑙 -20𝑓 𝑎𝑙𝑒𝑟𝑡_<𝑆𝐼𝐷>.𝑙𝑜𝑔 This helps detect: 𝐏𝐌𝐎𝐍 𝐟𝐚𝐢𝐥𝐮𝐫𝐞𝐬 Checkpoint termination Instance crash Startup/shutdown activities Background process issues 𝗚𝗼𝗹𝗱𝗲𝗻 𝗥𝘂𝗹𝗲 𝗳𝗼𝗿 𝗗𝗕𝗔𝘀: 𝗕𝗲𝗳𝗼𝗿𝗲 𝗱𝗲𝗲𝗽 𝘁𝗿𝗼𝘂𝗯𝗹𝗲𝘀𝗵𝗼𝗼𝘁𝗶𝗻𝗴, 𝗮𝗹𝘄𝗮𝘆𝘀 𝘃𝗲𝗿𝗶𝗳𝘆 𝗣𝗠𝗢𝗡 → 𝗢𝗣𝗘𝗡 𝗠𝗢𝗗𝗘 → 𝗜𝗡𝗦𝗧𝗔𝗡𝗖𝗘 𝗦𝗧𝗔𝗧𝗨𝗦 → 𝗔𝗟𝗘𝗥𝗧 𝗟𝗢𝗚. This simple checklist can save valuable production time. #OracleDBA #OracleDatabase #DatabaseAdministration #SQL #DBA #Oracle19c #ProductionSupport #AlertLog #Linux #DatabaseMonitoring #TechLearning #ITInfrastructure #CareerGrowth
To view or add a comment, sign in
No DBA doesn’t mean no database responsibility. Someone still needs to own: • Performance • Security • Backups Ignoring this can cost you more than just downtime. 👉 Need a quick database review? DM “DB” — let’s make sure you’re covered. #DatabaseManagement #DataSecurity #CloudDatabases #StartupTech #DataEngineering #DBA #TechLeadership #Zoftcorp
To view or add a comment, sign in
Make the best of today. Take a step forward, no matter how small, toward your goal. For your SQL environment, it may mean: * Documenting a restore process * Reviewing who has sysadmin privileges * Adding a failsafe operator to your SQL Server * Spending some time learning about a new feature * Asking a key stakeholder about the RPO/RTO for an application How can you make your SQL Server environment just a bit better today? #sqlserver #dba #remotedba #dataprotection #datasecurity
To view or add a comment, sign in
Fun #AprilFools post from the team — but in reality, preventing #SQLServer outages takes the right high availability strategy. #DBA #HighAvailability #SQLServer https://lnkd.in/gpYJVcii
DH2i #SQLServer Downtime CarePackages™ are here! If your database goes down, you get: ✔ A sympathy card ✔ A pizza for the on-call DBA ✔ A strongly worded email to your infrastructure team Just ask your rep about our Premium Empathetic Support Plan to learn more! (Or… avoid downtime altogether 😉) #AprilFools #SQLServer #DBA #HighAvailability https://lnkd.in/gsKxsv_U
To view or add a comment, sign in
My fellow DBA friends , has anyone heard of a 500 cluster resource limit on SQL Server 2019. 3 node cluster with synchronous comitt, 166 AG’s each having a listener, if so is there a safe way to up the limit, I confess I was not aware of this limit, never ran into this situation before…
To view or add a comment, sign in
Recently worked on patching an Oracle 19c RAC (Windows) environment with RU 19.29. Patching completed successfully, but an issue was observed during component validation. 📌 Patch Verification (dba_registry_sqlpatch): 38194382 SUCCESS OJVM RELEASE UPDATE: 19.29.0.0.251021 (38194382) 38111211 SUCCESS Windows Database Bundle Patch : 19.29.0.0.251021 (38111211) At first glance, everything seemed fine ✅ But during validation: 👉 All components were VALID except CATPROC and SDO 📌 Before Fix (dba_registry): COMP_ID STATUS ---------- --------- CATPROC INVALID SDO LOADING ⚠️ Patch was SUCCESS, but core components were not in a valid state. 🛠️ Initial Attempt: @?/rdbms/admin/utlrp.sql 👉 The process was taking longer than expected and did not resolve the issue. 🔍 Analysis: This indicated the issue was not just invalid objects, but related to component loading. 🛠️ Fix Applied: Step 1: @?/rdbms/admin/catproc.sql 📌 Intermediate State: COMP_ID STATUS VERSION ---------- --------- ---------- CATPROC LOADED 19.0.0.0.0 Step 2: @?/rdbms/admin/utlrp.sql 📌 Recompilation Status: OBJECTS WITH ERRORS ------------------- 81 📌 Final Status: COMP_ID STATUS ---------- --------- CATPROC VALID SDO VALID 🎯 Key Learning: Patch SUCCESS does NOT guarantee database health. ✔️ Always validate using DBA_REGISTRY ✔️ If utlrp.sql doesn’t resolve → investigate deeper ✔️ Sometimes component reload (catproc.sql) is required 💬 Have you ever seen a case where patching was SUCCESS but components were still INVALID? #Oracle #OracleDBA #Oracle19c #RAC #DatabaseAdministration #Troubleshooting #DBA #Learning
To view or add a comment, sign in