Business Intelligence Blogs

View blogs by industry experts on topics such as SSAS, SSIS, SSRS, Power BI, Performance Tuning, Azure, Big Data and much more! You can also sign up to post your own business intelligence blog.

«November 2015»

DirectQuery in Power BI Desktop

In the latest Power BI Desktop a new Preview features was released that now allows you to connect using DirectQuery to either SQL Server or Azure SQL Databases.  DirectQuery is a really neat feature that allows you to point to the live version of the data source rather than importing the data into a data model in Power BI Desktop. 

Normally when you want to get an updated dataset in the Power BI Desktop you would have to manually click the refresh button (this can be automated in the Power BI Service), which would initiate a full reimport of your data.  This refresh could take a variable amount of time depending on how much data your have.  For instance, if you’re refreshing a very large table you may be waiting quite a while to see the newly added data. 

With DirectQuery data imports are not required because you’re always looking at a live version of the data.  Let me show you how it works!

Turning on the DirectQuery Preview

Now, because DirectQuery is still in Preview you must first activate the feature by navigating to File->Options and settings->Options->Preview Features then check DirectQuery for SQL Server and Azure SQL Database


Once you click OK you may be prompted to restart the Power BI Desktop to utilize the feature.

Using DirectQuery in Power BI Desktop

Next make a connection either to an On-Premises SQL Server or Azure SQL database.

Go to the Home ribbon and select Get Data then SQL Server.


Provide your Server and Database names then click OK. ***Do not use a SQL statement.  It is not currently supported with DirectQuery***


From the Navigator pane choose the table(s) you would like to use.  I’m just going to pick the DimProduct table for this example and then click Load.  You could select Edit and that would launch the Query Editor where you could manipulate the extract.  This would allow you to add any business rules needed to the data before visualizing it.


Next you will be prompted to select what you want to connect to the data. Again, Import means the data

Read more

The Big Data Blog Series

Over the last few years I’ve been speaking a lot on the subject of Big Data. I started by giving an intermediate session called “Show Me Whatcha’ Workin’ With”. This session was designed for people who had attended a one hour introductory session that showed you how to load data, to look at possible applications … Continue reading The Big Data Blog Series
Read more

Basic Configuration: SourceSafe 2005 and SQL Management Studio 2005

  • 6 June 2011
  • Author: Keith Hyer
  • Number of views: 4195


Let's assume you have installed SQL Server 2005 client tools and the Visual Source Safe client on the same machine.  You're all updated, patched and ready to start some query writing.  Naturally ( it's natural - right? ) you want to have your code in source control.  "Even your queries related to the project?", you may ask.  Yes - even those.

If you open up SQL Management Studio and you don't see the source safe integration there, here is what you do.



First, go into SQL Server Management Studio's "Tools" menu and select "Options..." as shown here.

Options on the Tools menu

Next, open the "Source Control" node of the tree on the left-hand side of the window that opens.  Under it, select the "Plug-in Selection".  The screen should look similar to the one below.

Plug-in Selection

Now click on the "Current source control plug-in" drop down and select ( you guessed it ) "Microsoft Visual SourceSafe" from the list as shown below.

Selecting SourceSafe

Once selected, you should see 2 new items added under the "Source Control" node on the left-hand pane's tree like so.

Selection Complete

Finally "Ok" and close your way back to the main SQL Server Management Studio IDE.  You should be all set.

If you want to customize the way VSS behaves with your project, you may do so under the "Environment" and "Visual SourceSafe" nodes that are added to the options tree.




One thing I did find during this.  If you also have Visual Source Safe 6.0's client installed on the same machine, and you then try to Open Source Safe from SSMS - it seems to "pick" the 6.0 interface instead of the 2005 interface.  I have not dug into why that is yet.  If you happen to know - please leave a comment and a work-around ( and or link ) if you know of one. 

Categories: Blogs
Rate this article:
No rating

Please login or register to post comments.