Just finished 5 days SQL Server 2012 Integration Services and Analysis Services at Wipro Technologies, Kochi. Enjoyed teaching Microsoft BI tools, especially Analysis Services.
Working with Dimensions, Hierarchies, Partitions, Aggregations, etc. is really challenging.
Thanks to all participants at Wipro for inviting me. Trust we’ll be meeting in future as well…
A data source in SSIS package is something which helps us to connect to the source of data like RDBMS, CSV File, Excel File, etc. and pull the data out.
A data source is used when we’re using Data Flow task. I’m sure you know about the Data Flow task, which is widely used, almost in every package. :)
There are various data sources such as ADO.NET, OLE DB, Flat File, Excel File, Raw File, etc. We choose a data source based on our requirement, from where we’re going to pull the data out.
Today, we’ll be talking about OLE DB Source, which can connect to almost all kinds of existing data sources, whether it’s SQL Server or Oracle or SAP NetWeaver or Access, etc. OLE DB uses the Connection Managers behind the scene in order to connect to a data source. It’s not Data Source but a Connection Manager decides what kind of driver you’re going to use and what database or data source you’re connecting to.
We’re going to discuss how to export data into different spreadsheet in the same Excel file over here. We’re going to use SQL Server Integration Services 2012 and AdventureWorks2012 database. However, if you’re using earlier version like SSIS 2008 R2, It’ll be working perfectly fine. So, no worries!
I assume that you know how to create a package, what is Data Source, Data Destinations, etc. in SSIS.
Create a package and drag and drop a Data Flow task on Control Flow tab.
Today, we’re going to discuss how to implement One-to-One relationship between two tables in SQL Server. So, what does it mean? That’s pretty simple. We can simply go to Database Diagram option and drag Primary Key from master table and drop that on Foreign Key on child table…and that’s it. What’s the big deal???
Yes. It will definitely implement Foreign Key constraint but the cardinality will be One-to-Many by default. Here we get the problem. I wish to implement One-to-One cardinality rather One-to-Many. I tried a lot with available options but in vain. The SQL Server doesn’t provide any option where you can simply go and change the cardinality between tables.
Let’s discuss how to achieve this in SQL Server.
I’ve got two tables, named 1.) Customer, and 2.) CustomerContact as you can see in below image.