SQL Server Express does not include SQL Server Agent. That means: No Jobs engine No Maintenance Plans (Management → Maintenance Plans does not exist) The same applies to many shared SQL Server environments. If you need automated backups, you must implement your own scheduling solution. The Solution Create a batch file and schedule it using Windows Task Scheduler . The script: Accepts database name as parameter Accepts backup folder as parameter Generates timestamped filename Executes BACKUP DATABASE via sqlcmd Batch File Script @echo off set databaseName=%1 echo %databaseName% set backupFolder=%2 echo %backupFolder% for /f "tokens=2 delims==" %%a in ('wmic OS Get localdatetime /value') do set "dt=%%a" set "YY=%dt:~2,2%" & set "YYYY=%dt:~0,4%" & set "MM=%dt:~4,2%" & set "DD=%dt:~6,2%" set "HH=%dt:~8,2%" & set "Min=%dt:~10,2%" & set "Sec=%dt:~12,2%...

Today I performed an initial test of MongoDB Atlas , the managed MongoDB Cloud Cluster that can run on different cloud providers. The full setup — from cluster creation to a working connection — took roughly one hour. For a managed distributed database platform, that timing is impressive. Environment Setup The goal was simple: Create a MongoDB Atlas cluster Configure network access Create a database user Connect from a .NET application The cluster provisioning itself was straightforward. The UI is clear, and the workflow is linear: project → cluster → security → connection. Connecting MongoDB Atlas to a .NET Application I successfully connected the cluster to a .NET application using the official MongoDB driver. This was particularly satisfying because about half a year ago, in a previous company, we failed to make it work. At the time, the issue seemed complex. Now I know the root cause. It was only an incorrect connection string. No networking issue. No fir...

A few months after a major Windows 10 update, I started getting the most annoying notification ever: The message appeared randomly. No pattern. No clear cause. Just constant irritation. The Situation My system looked like this: Disk D: is removable. C: and E: live on the same HDD. Siblings. So my logical plan was simple: shrink C:, extend E:, silence the warning. Disk Management Reality I opened Disk Management and saw this: E: did not have the same options as other partitions. No “Extend Volume…” available. The “Smart” Attempt I shrank C: by 2GB using “Shrink Volume…”. Unallocated space appeared between C: and E:. Then began the classic “dance with tambourine around the campfire”: Move partition Merge attempt Allocate space Retry Nothing worked. Third-Party Tools Trial Search results pointed to third-party partition managers. I tested multiple vendors, including Paragon Hard Disk Manager and Macrium Reflect. None of th...