THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Browse by Tags

All Tags » Reporting Servi... » sql   (RSS)
  • When someone deletes a shared data source in SSRS

    SQL Server Reporting Services plays nicely. You can have things in the catalogue that get shared. You can have Reports that have Links, Datasets that can be used across different reports, and Data Sources that can be used in a variety of ways too. So if you find that someone has deleted a shared data source, you potentially have a bit of a horror ...
    Posted to Rob Farley (Weblog) by rob_farley on October 8, 2012
  • Stored Procedures with SSRS? Hmm… not so much

    Little Bobby Tables’ mother says you should always sanitise your data input. Except that I think she’s wrong. The SQL Injection aspect is for another post, where I’ll show you why I think SQL Injection is the same kind of attack as many other attacks, such as the old buffer overflow, but here I want to have a bit of a whinge about the way that ...
    Posted to Rob Farley (Weblog) by rob_farley on November 21, 2011
  • Spatial data from shapefiles (for T-SQL Tuesday #006)

    I’m giving a presentation on May 12th at the Adelaide .Net User Group, around the topic of spatial data, and in particular, the visualization of said data. Given that it’s about one the larger types, this post should also count towards Michael Coles’ T-SQL Tuesday on BLOB data. I wrote recently about my experience with exploded data, but what I ...
    Posted to Rob Farley (Weblog) by rob_farley on May 10, 2010
  • Re-running SSRS subscription jobs that have failed

    Sometimes, an SSRS subscription fails for some reason. It can be annoying, particularly as the appropriate response can be hard to see immediately. There may be a long list of jobs that failed one morning if a Mail Server is down, and trying to work out a way of running each one again can be painful. It’s almost an argument for using shared ...
    Posted to Rob Farley (Weblog) by rob_farley on March 17, 2010
Privacy Statement