Ever worked on a quick little project, come across what you assume is a common need and think "I'll just google up some code that someone else has written and then be off to the races"? Have you done this and not been able to find the code you're looking for? Well, that was me… Continue reading SSRS: Parse parameters column from ExecutionLog
gah. Why is some of this stuff so challenging in Tableau? You have a date and you want to format it as a string? Why? So you can concatenate it with another string perhaps? Maybe you're creating a calculated field to use in a label (that's what I was doing). Unfortunately, when you convert a… Continue reading Tableau: Format Date As String mm/dd/yyyy hh:mm
For Tableau requirements like: Allow user to choose "Last 7 Days", "Last 30 Days", etc. this is your ticket. It turns out one parameter and one calculated field are all you need.
Suppose you create an extract in your desktop version of Tableau and everything is running great. Then one of your peers casually asks "how big is that .tde file anyway?" You quickly check file explorer and discover the extract is not in the default location (What is the default path?). It seems like there should… Continue reading Tableau – Where is the path to my extract!?!
What is the default path for tableau extracts on a windows desktop? C:\Users\<your user name>\Documents\My Tableau Repository\Datasources For example mine is: C:\Users\psteffek\Documents\My Tableau Repository\Datasources Boom.
Yay! There's a GUI to execute SSIS packages! Boo! It's really hard to figure out how to pass variables through it! You may have seen a message that looked something like this: TITLE: SSIS Execution Properties ------------------------------ DTExec: Could not set Package.Variables[User::MyVarA].Value value to Data Source=DevServ1. ------------------------------ BUTTONS: OK ------------------------------ Here are the three most… Continue reading How To Set Variables Using The SSIS Execute Package Utility
As soon as I saw this error message I guessed the problem was related to using a temp table. What was surprising was that the error message actually said this but I didn't realize it until by chance I cut and paste the message into another window. Look below: Do you see the reference to… Continue reading Troubleshooting: SSIS Unable to retrieve column information from the data source. Make sure your target table in the database is available.
This is one scary looking error message: SSIS error 0x00084005 "the parameter type cannot be deduced because a single expression contains two untyped parameters @x and @P1" It's terrifying enough to make you think maybe you should quit your SSIS development career altogether. But wait... What's this? Perhaps you're getting this message for the same… Continue reading Troubleshooting: SSIS error 0x00084005 “the parameter type cannot be deduced because a single expression contains two untyped parameters @x and @P1”
Dear SQL Server Integration Services Team, Would it be possible to get a more specific error message than "There are some mapping errors on this path"? Your friend, Phil The tricky problem with this error is getting enough information to troubleshoot it. Here's a nice trick for you: Run the package. Wait. What? Why would… Continue reading SSIS: There Are Some Mapping Errors On This Path – Troubleshooting
As more and more companies are moving to heterogenous environments with both windows and unix systems the life of the Microsoft SQL Server developer is becoming much more interesting. For our recent data warehouse project I was asked to create a SQL Server 2012 Integration Services (SSIS) ETL package to output a text file for… Continue reading SSIS Export To UTF-8 or UNIX (or how to set your code page to output a flat file for unix)