Hi All,
I am so thrilled to see this content online for getting ourselves trained on SQL Server 2012. Find-out yourself about the contents of kit and downloads.
Customizing the Default Logging in SSIS
Hi Guys,
Sometimes definitions are wacky. I thought of writing this article on default logging where I could modify it with my application requirements. And guess what… “Customization with default logging” title rendered in mind.
Just for fun if you think about it, when you customize the default logging; it would be custom logging. But custom is also that where you define everything from scratch. So ultimately it makes 2 types of custom logging: one – by using somebody’s readymade logging work and extend it. And second – by developing it from the scratch. 🙂
Today I would show you, how you can tweak (1st type of custom logging :)) the “Default Logging Framework” of SSIS and turn into “Custom Logging“.
Well, it’s really simple.
First you set the “Default Logging” – just configure the “Logging” on control flow tab in SSIS and done. What SSIS does for you internally is following list:
The History of SQL Server
Hi Guys,
A nice video on “SQL Server History” 🙂
SQL Server provides all organizations with a highly secure and trusted data platform on which to efficiently develop and use a broad array of feature-rich solutions to address customers business imperatives, including business intelligence applications, server consolidation and compliance.
Thanks, Khilit
Singapore SQL User Group – Special Meet Up: “SQL Server for Private Cloud”
Hi Guys,
Singapore SQL User Group is running a special meet up with Microsoft’s visiting speaker from U.S.
Topic: SQL Server for Private Cloud
Primary Focus:
Many customers are deploying virtualized SQL Server in production environment. Join this session to find out about “SQL Server for Private Cloud“, a solution that is part of overall Microsoft Hybrid IT story.
It will cover new features & functionalities of SQL Server 2012, System Center 2012, and Windows Server “8” that greatly enhance the capabilities of database applications running in Microsoft Private Cloud and the steps on putting this solution in your customer environment.
Configuring “Merge Join” Task in SSIS
Hi All,
Today I would like to tell you the required settings to be done for using Merge Join in SSIS.
Merging the data from 2 different sources can be implemented in various ways. And that depends on many things like both sources are on same SQL server or on different SQL servers but available as linked server or one source is MS SQL Server and other is Oracle etc.
But apart from all these, you concentrate on mainly 2 things, which will quickly get your job done.
We know basic requirements of using “Merge Join” data flow component.
- Both sources should have data sorted.
- Columns which will take part in joining condition should have same metadata.
Now, how to configure “Merge Join” task. Just follow the steps explained in following scenarios.
Rocking “Catalog Views” in SQL Server 2012
Hi All,
Today I came across an article on MSDN regarding the meta-data of SQL Server objects which led me to the “Catalog Views“.
What is it?
“Catalog View” provides the information which is used by SQL Server Database Engine. So one thing is – “you can definitely trust this method“.
Moreover, Microsoft recommends this method for information retrieval because it is the most efficient way to obtain, transform, and present customized forms of this information. To make the information retrieval easier, Microsoft has categorized almost every object available in SQL Server in following catalog categories. (Pls see below).
You will also notice that some catalog views are using other ready-made views. Well, they are categorized in mainly 2 types: base views and derived views.
• The base view contains a subset of columns and a super-set of rows.
• The derived view contains a super-set of columns and a subset of rows.
SQL Server Database Keys: PrimaryKey, NaturalKey, ForeignKey, UniqueKey, CandidateKey, AlternateKey, CompositeKey, SuperKey, SurrogateKey
Hi Guys,
How are you doing?
Many a times during interviews I notice that candidates know lots of things but they really hesitate while talking about “SQL Server Database Keys“. And even if they know about keys, they fail to provide proper answers with examples. So, today I would like to summarize few definitions which every database developer should be aware of.
I am not going to explain each in details but this will sure give you enough confidence to generate your own examples during interviews 🙂
I am going to use the following table for example reference in below definitions. Forget about the proper table design because we need only these columns for demo.
Table name : Employee (Parent Table)
Columns :
- Id (Identity column of table )
- Emp_Id (Employee’s Id Number given by a company/organization)
- Emp_SSN (Employee’s Social Security Number)
Table Name : EmployeeDetails (Child Table)
Columns :
- id_EmployeeDetails (PrimaryKey of table)
FREE EBook from Microsoft Press – Introducing Microsoft SQL Server 2012
Hello guys,
Go and grab an opportunity to download latest & FREE eBook from Microsoft Press on SQL Server 2012. you can download it here. Or you can simply Google it to find out more sources 🙂
What ?? There is a “Ghost” in SQL Server !!!
Yes, it’s a cleanup process available as a part of SQL Server Storage Engine. It runs in background to cleanup ghost records. If you can remember … “When we create a clustered index then it stores actual data/records at the leaf level of the index.” And SQL Server marks/declares a record as a ghost records when they are deleted from leaf level of index.
Why just mark and not to delete at once even though SQL Server knows that user does not need that record anymore ?? Well, to achieve better performance SQL Server runs “Ghost Cleanup Task” asynchronously to permanently delete marked records.
Though the ghost cleanup task is one of the internal processes of SQL Server, it does not override the locking framework laid-out in SQL Server. That means … the ghost cleanup task can’t delete the marked records for deletion until and unless the lock has released which is acquired by user’s delete transaction. Once the delete transaction is committed, ghost cleanup task permanently erase these records.
What happens to IDENTITY Column Value When SQL Transaction Fails??
Hi All,
I would like to share a simple interview question. This is very simple yet many developers overlooks or not taking care of it.
Do you know what happens to identity value if transaction fails? Do you think that identity value of table is unchanged after failure?
Before looking at the solution below, try to memorize ACID properties of transaction and answer it.
Check-out the POC shown below & wobble your mind 🙂