How to read data from multiple Excel worksheets with SQL Server Integration Services
Read this tip to learn how to import data from multiple Excel worksheets into SQL Server using SSIS.
Read this tip to learn how to import data from multiple Excel worksheets into SQL Server using SSIS.
An evaluation of the SQL Azure Database Performance Levels recommended by the DTU Calculator service, and a comparison with on premise SQL Server performance.
We have an operating system for how our organizations are run. Steve Jones talks about a new one that might be important for the world rules by software.
In-Memory OLTP has evolved to be a great solution. However, a production system that uses it needs careful monitoring to avoid stress conditions becoming problems. As with many new features of SQL Server, it pays to plan a monitoring strategy to ensure that you are alerted as soon as possible when things go awry.
The idea of using a queue in a database is one that some people try to avoid, preferring to use a messaging service. However, Steve Jones notes that this isn't always necessary.
Now that we have our database under source control, we will want to share our work with other developers. If we are in a centralized source control system, our changes may be committed straight into the central repository.
When we are working in a distributed system, it means pulling down any changes from other developers, addressing any areas of conflict, and pushing our changes up to allow others to benefit from our work. This allows our changes to be synchronized with the changes other developers have made.
This level is principally about setting up a distributed source control system, namely Git, and how to commit database development changes to a local repository, before pushing them into a remote 'central' repository for sharing with other developers.
The next level will delve a little deeper into Git's versioning mechanisms, and show some examples of how to share database changes during development, and how to deal with conflicting changes.
Jeremy Kadlec introduces the Enhanced Data Integration Suite (EDIS), a SQL Server T-SQL stored procedure based solution to automate, manage, and audit ETL processes so you no longer have to manually build SSIS Packages.
It's hard to build strong security over time, but it's worth the effort. Steve Jones notes that even smart people have problems implementing strong security.
From an IT infrastructure and compliance perspective, the importance of protecting data is clear. But it also has profound business implications and can even be a competitive differentiator by helping drive customer loyalty and retention. David Hobbs-Mallyon talks about Microsoft’s approach to data security.
Rodney Landrum gets lost in the fourth dimension, while coding the infinite possible combinations of SQL Server dates and times.
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
By Brian Kelley
On Patch Tuesday, in addition to OS and Office security patches, Microsoft also released...
Comments posted to this topic are about the item Multiple Deployment Processes
Comments posted to this topic are about the item How to Use sqlpackage to...
Comments posted to this topic are about the item Upgrading Admin Queries
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers