The second part of a great data warehousing series from Vincent Rainardi looks at the decision to stage data prior to moving it into the warehouse versus directly loading it. This is a must read for those contemplating a data warehouse.
Throughout our series of articles dedicated to SQL Server 2005 Integration Services, we have been working mainly with packages using the Business Intelligence Development Studio interface (although more recently, we also discussed SSIS-related functionality available in SQL Server Management Studio). Even though, as part of our exercises, we have worked with a number of packages, we have not yet explored the various options related to their storage. We will cover them in this article
One thing that many people tried to implement in SQL Server 2000 is the auditing of logins. However getting this to work was a complex process. In SQL Server 2005, however, there are a few ways you can handle this and new author Frederik Vandeputte brings us a method using Service Broker for handling this.
In SQL Server 2005, you can explicitly or implicitly define the execution context. As we all know, a session starts when a user logs on to SQLServer or a connection to SQLserver is made. All operations in that session use the logon credentials used for connecting to SQL Server. When an EXECUTE AS statement is run, the execution context of the session is switched to the specified login or user name.
Have you started looking at what issues you might have migrating your existing applications to SQL Server 2005? If not then maybe as a first step, you should consider looking into what the SQL Server 2005 Upgrade Advisor can do for you. This article will discuss what the Upgrade Advisor is and how to use it.
You have many SQL Servers to administer and you just want to know when the last backup was taken for each database on each instance. This stored procedure will help.
What is the most efficient way of generating a range of values? SQL Server guru David Poole takes a look at a few different methods, both procedural and set based, and gives you some performance results.
Learn about SQL Server security techniques including the principle of least privilege, controlling metadata visibility, separation of users and schemas, and more.
By Steve Jones
I wrote an article recently on the JSON_OBJECTAGG function, but neglected to include an...
By HeyMo0sh
After working deep in cloud operations, I’ve learned that FinOps isn’t really about dashboards...
By gbargsley
Hello, dear blog reader. Today’s post is coming to you straight from the home...
Comments posted to this topic are about the item Creating a JSON Document I
Comments posted to this topic are about the item Who is Irresponsible?
Comments posted to this topic are about the item Designing Database Changes Before Deployment:...
I want to create a JSON document that contains data from this table:
TeamID TeamName City YearEstablished 1 Cowboys Dallas 1960 2 Eagles Philadelphia 1933If I run this code, what is returned?
SELECT json_objectagg('Team' : TeamName)
FROM dbo.NFLTeams;
See possible answers