In the ridiculously titled post I hold this blog hostage for 1 million views mahaaahaha mahahaha…. I told you that it took me a little over 3 years to reach 1 million views. I also said that I hoped to get the next million within 2 years, it actually took 1 year and 8 months. In between I have added 186 posts, the average views per post went from 2,739 to 3,629

And it is time again for another "stupid me"! For those unfamiliar with the concept: Every time I do something "stupid", which happens from time to time, I'll do a little blog post on what happened and how I solved it. The reason for this is twofold: I'll have a solution online I can consult if it happens again and other people can benefit from my mistakes as well. Because remember the ancient Chinese proverb: "It's only stupid if you don't turn it into a learning experience". Okay, I might have made that last one up...

Does it every bother you when you use the Arrow Keys to move an object in your SSRS report that it jumps much further over than you really wanted? Maybe you just wanted to nudge it a few pixels to the left but instead it is now over lapping the next object. I used to think that I had to either use my mouse to move it over or start playing with the position coordinates in the properties of the object.

When creating a SSRS report, you want to add lines that display trends. You want to show trends for more than one data point. And you want to conditionally format the data point. In this example, I use Sparklines and a simple expression to create a sparkling report! Below is how the Sparkline with multiple data points and conditional formatting applied to them will look like. Columns represent sales by month and line represents sales quota by month. Column is in green when sales exceeds the quota for a given month and red when sales fall below the quota.

This blog is part of my series Making Data Tell a Story With SSRS Properties. Property: Label – Visible The purpose of this property is to show the values of data points in the series on a chart. To access the property, go to the chart series properties, expand Label, and go to Visible. Example: I have a chart that shows sales by year, with a series for each product category.

Microsoft has made available the Windows Azure Training Kit The Windows Azure Training Kit includes hands-on labs, presentations, and samples to help you understand how to build applications that use Windows Azure. Hands-on labs are sets of step-by-step guides that are designed to help you learn how to use key Windows Azure services and features. Each Lab provides instructions to guide you through the process of developing a complete application. The cool thing is that you can contribute to any of these hands-on labs by forking their repositories on GitHub and make changes to the content. Once you’ve made your changes, share them back with the community by sending a pull request.

This blog is part of my series Making Data Tell a Story With SSRS Properties. Property: Tooltip The purpose of this property is to show a specific value on a series in a chart when the user hovers over the data point. To access the property, select a chart series and go to Tooltip. Example: I have a line chart that shows sales by category by year. I want the user to be able to see the exact value as a tooltip.

When you install SQL Server, Setup will write a set of default startup options to the Windows registry. You can use the startup options to specify an alternate master database file, master database log file, or error log file. Here is what the default options are according to Books on line Default startup options <th> Description </th> </tr> <tr> <td> <p> <strong>-d </strong><span class="parameter">master_file_path</span> </p> </td> <td> <p> The fully qualified path for the master database file (typically, C:Program FilesMicrosoft SQL ServerMSSQL.<span class="parameter">n</span>MSSQLDatamaster.mdf). If you do not provide this option, the existing registry parameters are used. </p> </td> </tr> <tr> <td> <p> <strong>-e </strong><span class="parameter">error_log_path</span> </p> </td> <td> <p> The fully qualified path for the error log file (typically, C:Program FilesMicrosoft SQL ServerMSSQL.<span class="parameter">n</span>MSSQLLOGERRORLOG). If you do not provide this option, the existing registry parameters are used. </p> </td> </tr> <tr> <td> <p> <strong>-l </strong><span class="parameter">master_log_path</span> </p> </td> <td> <p> The fully qualified path for the master database log file (typically C:Program FilesMicrosoft SQL ServerMSSQL.<span class="parameter">n</span>MSSQLDatamastlog.ldf). If you do not specify this option, the existing registry parameters are used. </p> </td> </tr> If you want to get the startup parameters for SQL Server, you can either read the registry or open up SQL Server Configuration Manager and look at the Startup Parameters tab, here is what it looks like on my laptop

MongoDB ships with a web-based administrative tool. You can see this tool by going to http://localhost:28017/ You can see a bunch of stuff on the administrative tool screen. here is a partial image. There are a bunch of links that you can click as well. If you click on any of the links on top `List all commands | Replica set status Commands: buildInfo cursorInfo features hostInfo isMaster listDatabases replSetGetStatus serverStatus top` You get the following message

To list all the tables that are partitioned you can use the sys.partitions view. However be aware that all tables and indexes in SQL Server contain at least one partition, whether or not they are explicitly partitioned. If you were to do the following, you would get back every table SELECT partition_number,rows,object_name(object_id) FROM sys.partitions So what can you do? Let’s take a look. First we are going to create a partitioned table in case you don’t have one so that you can get the same output as me.