Technical Article

Building a Data Foundation for a BI Solution

August 2009
Business Intelligence: Planning Your First Microsoft BI Solution
Even BI novices can learn what goes into creating a BI solution, from planning and designing a data mart to preparing data. An Adventure Works example illustrates the first steps a company can take to ensure that its BI solution supports the strategic decisions it needs to make. Stacia Misner
Business Intelligence: Building a Data Foundation for a BI Solution
See how you can design and build a data mart that uses SQL Server 2008 Integration Services to perform the extract, transform and load (ETL) processes for the Adventure Works BI solution introduced in "Planning Your First Microsoft BI Solution." Derek Comingore

Blogs

How to Install DBeaver and Connect to a PostgreSQL Instance

By

Whether you’re a seasoned DBA or just exploring database tools, DBeaver offers a powerful,...

DBAs should never run SSMS under their everyday Windows account

By

 DBAs should never run SSMS under their everyday Windows account If you open SSMS under...

macOS Tahoe breaks SQL Server on Docker containers on Apple silicon

By

The honeymoon is over, and macOS 26 Tahoe broke the Rosetta 2 emulation layer...

Read the latest Blogs

Forums

Extract from sql.to multiple sheets

By Sqladmin1

Import-Module ImportExcel # Path to your .sql file $sqlFile = "C:\Data\MyQueries.sql" $excelPath = "C:\Data\SqlExtract_$(Get-Date...

sp_prepare and sp_execute vs sp_executesql

By rajemessage 14195

I have noticed sp_executesql also makes a single plan for a stmt with parameter...

Who am I?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Who am I?

Visit the forum

Question of the Day

Who am I?

If I want to track which login called a stored procedure and use the value in an audit, what function can I use to replace the xxx below?

create procedure AddNewCustomer
  @customername varchar(200)
AS
BEGIN
    DECLARE @added VARCHAR(100)
    SELECT @added = xxx

    IF @customername IS NOT NULL
      INSERT dbo.Customer
      (
          CustomerName,
          AddedBy 
      )
      VALUES
      (@customername, @added)
END

See possible answers