Operations | Monitoring | ITSM | DevOps | Cloud

The SQL Server GETDATE() function grabs the current date and time of the server down to the millisecond. This makes it perfect for general timestamping, logging events, and simple date/time math. But what about time zones or when you need a rock-solid, consistent timestamp? Is GETDATE() enough, or do you need something else, like CURRENT_TIMESTAMP? In this article, we’ll show you how and when to use GETDATE() in SQL.

SQL Server DROP INDEX is a command you’ll find yourself using regularly as you manage and optimize your databases. Indexes are important for performance, but they’re not a “set it and forget it” kind of thing. Sometimes, an index becomes obsolete, redundant, or even detrimental. That’s when you need to know how to use the DROP INDEX SQL statement effectively.

As someone who’s worked with SQL Server databases, you know there’s no margin for error. A single discrepancy between environments can cascade into a failed deployment, broken workflows, or inaccurate reports. And let’s face it, manually comparing schemas and data isn’t just tedious; it’s risky. This is where industry-leading database comparison tools come to the rescue, turning a frustrating, time-consuming process into a smooth and efficient one.

SQL Server data types are the foundation upon which your entire database structure rests. They define the kind of data you can store in each column, from simple integers and text strings to complex date/time values and binary data. Picking the right SQL data type means your data is stored efficiently, queries run fast, and your information stays accurate. Using an overly large data type wastes space and slows things down, while using a too small type risks data loss or errors.

Dealing with different data sources without efficient data integration tools turns valuable information into a liability. These solutions give you a unified view of your data, eliminating silos and ensuring data consistency, accuracy, and accessibility. But, where do you start? Navigating the 2025 data integration market, with the shift towards scalable cloud platforms, self-service integrations, and AI automation, can be tough.

Progressive Delivery strategies like Blue/Green deployments, canary releases, feature flag rollouts, and feature delivery platforms help teams release safely, limit risk, and accelerate learning. Each approach builds toward sustainable, high-velocity software delivery by minimizing downtime and maximizing feedback. Combining these methods enables faster innovation with greater confidence and control. Last week we walked The Path To Progressive Delivery. This week, we go deeper.

We are happy to announce our latest project at MetricFire: a brand-new CLI tool! Get ready to start monitoring your systems in one step - no need to modify any configuration files manually. Just run a terminal command, follow the prompts, and forward your system metrics to Hosted Graphite in minutes. In this article, we’ll share an overview of the Hosted Graphite CLI, why we’re making it, and how we’re making it.

When evaluating CI/CD platforms, it can be easy to view them as commodities — interchangeable tools that accomplish the same basic tasks. But as development teams scale, small differences in platform performance can be compounded, significantly impacting development velocity and resource utilization. To better understand these differences, we conducted a head-to-head comparison between CircleCI and GitHub Actions, focusing specifically on performance at enterprise scale.

When I joined Checkly as Junior People Operations Manager, one of the benefits that immediately stood out to me was the Learning & Visiting budget. I found myself wondering—how is this budget actually being used across the company? At the start of the year, many of our team members plan how they’ll use their learning budget—whether to enhance professional skills or pursue self-driven projects. With flexible guidelines, we encourage them to invest in what matters most.