SQL Server Integration Services (SSIS) is the integration and ETL (extract – transform – load) tool in the Microsoft Data Platform stack. SSIS is typically used in data warehousing scenarios, but can also be used in common data integration use cases or just to move data around. SSIS is used behind the scenes in the Maintenance Plans of SQL Server and in the Import/Export wizard.
Steve Jones talks about learning, teaching, and the need to not waste anyone's time.
There are several obvious problems with poor SQL Coding habits. It can make code difficult to maintain, or can confuse your team colleagues. It can make refactoring a chore or make testing difficult. The most serious problem is poor performance. You can write SQL that looks beautiful but performs sluggishly, or interferes with other threads. A busy database developer adopts good habits so as to avoid staring at execution plans. Rob Sheldon gives some examples.
Steve Jones notes that we often solve problems better the second time around.
Azure Data Factory is a cloud based data integration service. This helps you to define, schedule and manage data pipelines to transfer and transform the data from disparate on premise and cloud data sources. Read on to learn more.
In this article we will learn to use Data Factory to import table from SQL Server to Azure SQL Data Warehouse.
Microsoft (StreamInsight), and Azure Stream Analytics represent a very different model for processing data. They are concerned with processing complex event streams of data (CEPs) from such things as sensors to deduce significant patterns and apply filters. Joe Celko discusses the background to an intriguing technology of complex event processing to establish the difference between data at rest, and data on the move.
Even the most elaborate team-based development methodology won't compensate for the blinkered attitudes and tribal cultures that come from over-specialization in IT.
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers