Technical Architects Zone

  🗄️ 𝗦𝗤𝗟 𝗦𝗲𝗿𝘃𝗲𝗿 𝗔𝗱𝗺𝗶𝗻𝗶𝘀𝘁𝗿𝗮𝘁𝗶𝗼𝗻 | 𝗗𝗮𝘁𝗮𝗯𝗮𝘀𝗲 𝗖𝗿𝗲𝗮𝘁𝗶𝗼𝗻 Creating a database in SQL Server looks simple: "CREATE DATABASE TAZDemo;" But for a Database analyst or DBA, database creation is much more than running just a command. Before creating a production database, we need to think about: 🔹 MDF, NDF and LDF files 🔹 Initial data and log file sizing 🔹 Autogrowth configuration 🔹 Fixed MB vs percentage growth 🔹 Data and transaction log placement 🔹 Database owner 🔹 Recovery model 🔹 Storage capacity and future growth 🔹 Backup and recovery requirements One principle worth remembering: 💡 Autogrowth is a safety mechanism, not a capacity-planning strategy. In my latest Technical Architects Zone (TAZ) article, I’ve explained database creation step by step using both SSMS and T-SQL , along with practical checks and production considerations. 📖 𝗥𝗲𝗮𝗱 𝘁𝗵𝗲 𝗰𝗼𝗺𝗽𝗹𝗲𝘁𝗲 𝗮𝗿𝘁𝗶𝗰𝗹𝗲: 👉 SQL Server administration - Database creat...

TECHNICAL ARCHITECTS ZONE PostgreSQL Architecture: A Comparison with SQL Server A practical architecture guide for SQL Server DBAs, database administrators, architects and technology professionals beginning their PostgreSQL journey. Whether you are a SQL Server DBA, database administrator, cloud engineer, architect or developer, understanding PostgreSQL architecture is an important foundation for administration, troubleshooting, performance tuning, backup and recovery, replication and high availability. PostgreSQL and SQL Server are both enterprise relational database platforms, but their internal architecture and operational models are different. SQL Server primarily uses a thread-based execution architecture within the database engine process, while PostgreSQL traditionally uses a process-based architecture in which client connections are ...

TECHNICAL ARCHITECTS ZONE SQL Server Performance Troubleshooting A practical collection of SQL Server scripts and diagnostic techniques for investigating CPU, I/O, blocking, waits, memory, TempDB and query-performance issues. Performance issues are among the most common challenges handled by SQL Server DBAs. A typical incident starts with a broad statement such as “the application is slow,” but that statement does not identify whether the underlying problem is blocking, CPU pressure, storage latency, memory pressure, TempDB contention or an inefficient query. Effective troubleshooting begins by collecting evidence from SQL Server before making configuration or application changes. This article provides practical Dynamic Management View queries that can help identify where to begin. TAZ Practical Note Capture evidence ...

  Most cloud migration projects don't fail because of technology. They fail because the wrong migration strategy was chosen from day one. Should you simply move the database? Should you modernize it? Should you redesign the application? Or should you replace it entirely? For database architects, choosing the right migration path is often more important than the migration itself. Why Database Migrations Fail Underestimating data volume Ignoring dependencies Downtime assumptions Performance surprises Security and compliance gaps Database Migrations Strategies:      1. Rehost ("Lift and Shift") -  Move the workload as-is with minimal changes.      Example:      SQL Server on VM >>  SQL Server on Azure VM or SQL Server on GCP Compute Engine or EC2 in AWS     Pros:           ✅ Fastest migration           ✅ Lowest initial effort     Cons:  ...