External Article

Migrating Microsoft Access Databases to SQL Server 2008

Microsoft Access is a very good database solution, but it has limits. While the portability of mdb and accdb files is convenient, there are advantages to moving to the less portable SQL Server solution. If you do have SQL Server, there's very little reason not to consider migrating your Access Databases. Not all custom-made Access applications easily lend themselves to a SQL Server solution so you'll need to do some analysis before choosing a migration path.

Blogs

Learn about Modern Microsoft Apps in San Diego

By

I wrote about learning today for the editorial: I Can’t Make You Learn. I...

How To Deploy Fabric SQL and Azure SQL Databases with Azure DevOps

By

Fabric has CI/CD built in, but if you've tried to use it for database...

A New Word: Attriage

By

attriage – n. the state of having lost all control over how you feel...

Read the latest Blogs

Forums

Forward Deployed Engineers

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Forward Deployed Engineers

TRY_PARSE vs TRY_CONVERT in SQL Server: From Basics to Practical Usage

By john.martin

Comments posted to this topic are about the item TRY_PARSE vs TRY_CONVERT in SQL...

DBCC CHECKDB Limits II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DBCC CHECKDB Limits II

Visit the forum

Question of the Day

DBCC CHECKDB Limits II

I have a SQL Server 2025 database that I want to check for corruption every night. One of the things we do is disable indexes used for ETL loads during the weekend and re-enable them on Monday morning. If we run DBCC over the weekend, are our disabled indexes checked for consistency?

See possible answers