External Article

SQL Server Integration Services (SSIS) - Design Best Practices

In the previous tips (SQL Server Integration Services (SSIS) - Best Practices - Part 1, Part 2 and Part 3) of this series I briefly talked about SSIS and few of the best practices to consider while designing SSIS packages. Continuing on this path I am going to discuss some more best practices of SSIS package design, how you can use lookup transformations and what considerations you need to take, the impact of implicit type cast in SSIS, changes in SSIS 2008 internal system tables and stored procedures and finally some general guidelines.

Blogs

The Agent Era: When “How do I…?” Replaces “Where do I click?”

By

After a year away getting to grips with AI and its application across the...

Beware of Generic SQL Server License Keys (What to Use Instead)

By

Beware of Generic SQL Server License Keys (What to Use Instead) ...

On Speaking Well

By

Professor Patrick Winston of MIT used to give a one-hour talk about how to...

Read the latest Blogs

Forums

Creating a JSON Document II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Creating a JSON Document II

Backing Up Azure Key Vault EKM Key: Stairway to TDE Level 6

By VishnuGupthanSQLPowershellDBA

Comments posted to this topic are about the item Backing Up Azure Key Vault...

Every Database Has Problems

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Every Database Has Problems

Visit the forum

Question of the Day

Creating a JSON Document II

I want to create a JSON document that contains data from this table:

TeamID TeamNameCity         YearEstablished
1      Cowboys  Dallas       1960
2      Eagles   Philadelphia 1933
3      Packers  Green Bay    1919
4      Chiefs   Kansas City  1960
If I run this code, what document(s) is/are returned?
SELECT json_objectagg( n.city : n.TeamName)
FROM dbo.NFLTeams;

See possible answers