Performance Myths: Oversizing string columns
Aaron Bertrand shows a quick demo that illustrates why you should be very careful about oversizing varchar / nvarchar columns.
2017-07-13
7,641 reads
Aaron Bertrand shows a quick demo that illustrates why you should be very careful about oversizing varchar / nvarchar columns.
2017-07-13
7,641 reads
How can we be sure that the new DBAs are productive a soon as possible? How can we use highly qualified contractors in the most effective way from day one?
2017-07-12
3,599 reads
To achieve gains from Database Lifecycle Management in general, and in Continuous Deployment in particular, it pays to aim for lightweight but consistent techniques and processes, refining them iteratively in the light of experience. Edward Elliott describes a Test-driven development process for developing SQL Server databases that worked for CD, based on a series of steps. Though the tools for CD may be necessary, they are not sufficient, without an effective structured process.
2017-07-11
3,560 reads
One of the key tenets in DevOps is to involve the Operations team in the full software development lifecycle and, in particular, to ensure that operational requirements are incorporated...
2017-07-11
4,304 reads
The majority of Azure SQL Database related features reach their General Availability (GA) stage relatively quickly. There are however, some exceptions. The most prominent example in this category is likely Azure SQL Data Sync, which has remained in Preview since its introduction 7 years ago. Fortunately, there are signs that this service might be finally reaching production-ready state. In this article, Martin Pollicht introduces its main characteristics.
2017-07-10
2,856 reads
Jonathan Kehayias discusses SQL Server on VMware, and how to monitor CPU performance – with or without access to vCenter.
2017-07-07
5,127 reads
There are multiple ways to accomplish a database restore. But if you wanted to restore a database from a script how might you accomplish that task quickly and accurately?
2017-07-06
3,891 reads
TSQL Code must work properly and efficiently. That's not enough though. Unless you are working alone, have perfect memory and plan to never change job, then you need to comment and document your code, it must be inherently readable, well laid out, use informative and obvious names, and it must be robust and resilient; written defensively. It must not rely on deprecated features of SQL Server, or assume particular database settings. Robert Sheldon starts a series of articles that explains the basics.
2017-07-05
7,732 reads
In this post, Tim Smith looks at the different options you can use to audit your SQL Server extracts and loads during the ETL process.
2017-07-04
3,755 reads
What native SQL Server options are available to export to Excel? Jeremy Kadlec explains.
2017-06-30
5,930 reads
By Steve Jones
One of the language changes in SQL Server 2025 that I’ve seen a lot...
By Steve Jones
I hosted this month, but I decided to put my own entry in as...
By Chris Yates
I get asked a lot about why or how I began working with databases...
Comments posted to this topic are about the item Getting the Object Code
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
Comments posted to this topic are about the item Being Mindful of Design Time
What happens when I run this on SQL Server 2022 in the AdventureWorks2022 database?
SELECT OBJECT_DEFINITION (OBJECT_ID(N'dbo.uspGetBillofMaterials')) AS [Object Definition]; GOSee possible answers