Search results matching tags 'SSIS' and 'SSRS'

Build-time dependency resolving coming to Entity Framework. Now, how about those BI tools too?

jamiet — Tue, 07 Dec 2010 10:04:00 GMT

Three months ago I wrote a blog post entitled Some thoughts on Visual Studio database references and how they should be used for SQL Server BI where I shared some thoughts on a feature available to database developers in Visual Studio 2010 that I would love to see added to SQL Server Integration Services (SSIS), Analysis Services (SSAS) and Reporting Services (SSRS). In there I said:

Over the past few weeks I have been making heavy use of the Database tools in Visual Studio 2010 and one of the features that has most impressed me has been database references.

Database references allow you to have stored procedures in your database project that refer to objects (tables, views, stored procedures etc…) that exist in other database projects and hence when you build your database project it is able to resolve those references.

It occurred to me that similar functionality would be incredibly useful for SQL Server Integration Services(SSIS), Analysis Services (SSAS) & Reporting Services (SSRS) projects. After all reports, packages and data source views are rife with references to database objects – why shouldn’t we be able to have design-time dependency checking in our BI projects the same way that database and .Net developers do?

In that blog post I shared links to three Connect submissions where I requested this feature be added to SSIS, SSAS & SSRS. In addition I also submitted a request that the feature be extended to .Net projects so that any reference to a database object in a .Net assembly can be resolved at build time. That Connect submission is at [Entity FX] Use database references to constrain the EDM and overnight it received this comment from Microsoft:

We have been working on this feature for a while and and will be available soon

This is really good news - it improves the Microsoft developer ecosystem by ensuring invalid references to database references get caught at build time (ideally as part of a Continuous integration build) rather than run time. [Hopefully it might nip this code-first nonsense in the bud too (Ooo...way to incite flame comments :) ) ]. If you want to see this feature in action then check out a video from Teched Europe last month entitled SQL Server Developer Tools Code-named "Juneau" where it is demo'd by Lance Delano and Tim Laverty.

The point of this blog post though is not just to draw attention to this forthcoming feature for .Net developers, it is to ask you to petition Microsoft to get this feature added to SSIS/SSAS/SSRS too. After all, we already know (from the video above) that the feature is coming to this new code-name Juneau development environment plus we also know that Juneau will be the development environment for SSIS/SSAS/SSRS as well - is it really much of a stretch to expect the BI tools to have access to this great feature too? I don't think so and if you agree with me then I urge you to vote and add a comment to the Connection submissions that are requesting this feature. They are at:

[SSAS] Declare Object Dependancies
[SSRS] Declare Object Dependancies
[SSIS] Declare Object Dependancies (Update, Apparently someone at Microsoft has deemed it necassary to set this to private and I am not able to change it back even though I submitted it. You can still vote on the other two though.)

Let's close that SQL Developer Gap!

@Jamiet

SQL Server v.Next (Denali) : Launch point for BI resources

AaronBertrand — Wed, 01 Dec 2010 01:23:00 GMT

Microsoft's new data platform vision for BI is called BISM - Business Intelligence Semantic Model. While I focus primarily on manageability, availability and database engine features, I'd like to keep tabs on who can help you out with their input on the other aspects I rarely touch - Analysis Services (SSAS), Integration Services (SSIS), and Reporting Services (SSRS). Since I'm not covering these areas in my "What's New in Denali" presentations, I thought it would only be fair to provide a decent launch point So here are some blogs, individual posts and other resources with great information - if you have any other resources, please let me know! Here is what I have come up with so far, in no particular order:

Jen Stirrup has some thoughts on BISM that are definitely worth a read:

http://www.jenstirrup.com/search/label/denali

Chris Webb also talks about BISM and its unification with SSAS:

http://cwebbbi.wordpress.com/2011/05/17/good-news-on-the-future-of-analysis-services/

The AS & PowerPivot team blog also has some information about BISM and SSAS:

http://blogs.msdn.com/b/powerpivot/archive/2011/05/16/analysis-services-vision-amp-roadmap-update.aspx

Rafael Salas talks about a lot of SSIS topics as they relate to Denali:

http://www.rafael-salas.com/search/label/Denali

Robert Bruckner of the Reporting Services team answers many questions about Project "Crescent":

http://blogs.msdn.com/b/sqlrsteamblog/archive/2010/11/09/a-glimpse-at-project-crescent.aspx

Chris Webb lists some great talking points about SSAS, with some excellent comments as well:

http://cwebbbi.wordpress.com/2010/11/11/pass-summit-day-2 /
http://cwebbbi.wordpress.com/2010/11/14/pass-summit-day-2-the-aftermath /

TechNet Wiki has some great stuff on SSIS enhancements in Denali on the new SSIS Catalog ("SSISDB") and usability enhancements:

http://social.technet.microsoft.com/wiki/contents/articles/sql-server-denali-ctp1-integration-services-ssis-catalog-overview.aspx
http://social.technet.microsoft.com/wiki/contents/articles/sql-server-denali-ctp1-integration-services-ssis-usability-enhancements.aspx

Jacob Sebastien has created a "What's New in Denali" resource page that has plenty of BI-related information:

http://beyondrelational.com/whatisnew/sqlserver/denali/

Watching the Denali tag on this site could be useful, even though most of the posts so far do not relate to BI:

http://sqlblog.com/search/SearchResults.aspx?q=denali&o=DateDescending

While during CTP periods, Books Online is rarely in sync with the actual build that is out there, it can still contain quite a bit of information. Here is the starting point for "What's New" in Denali:

http://msdn.microsoft.com/en-us/library/bb500435%28v=SQL.110%29.aspx

And you can download the latest "offline" version of Books Online here:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a94fd771-9e65-4afa-9c5f-03344c48133f

The official SQL Server "Denali" site - more marketing than tech, but still useful:

http://www.microsoft.com/sqlserver/en/us/product-info/future-editions.aspx

And here is MSDN's Denali Resource Center:

http://msdn.microsoft.com/en-us/sqlserver/denali_resource_center.aspx

If you're looking for help, the SQL Server community is a vast and generous resource. Post your question under the appropriate twitter hashtags:

#SQLHelp
#SQLDenali
#SQLServer
#SSAS
#SSIS
#SSRS

And don't forget the TechNet forums:

http://social.technet.microsoft.com/Forums/en-US/category/sqlserverprerelease

Finally, if you'd like to provide feedback, submit suggestions, or file bugs, please use Connect (you'll need a LiveID):

http://connect.microsoft.com/sql

Some thoughts on Visual Studio database references and how they should be used for SQL Server BI

jamiet — Tue, 14 Sep 2010 12:53:00 GMT

Over the past few weeks I have been making heavy use of the Database tools in Visual Studio 2010 (formerly known as datadude, DBPro, VSTS for Database Professionals or one of a plethora of other names that it has gone by over the past few years) and one of the features that has most impressed me has been database references.

Database references allow you to have stored procedures in your database project that refer to objects (tables, views, stored procedures etc…) that exist in other database projects and hence when you build your database project it is able to resolve those references. Gert Drapers has a useful introduction to them at his blog post Database References; in his words database references allow you to:

represent and resolve 3 and/or 4-part name usage inside a database project. Database references are conceptually the same as assembly references inside a C# or VB.NET projects; they allow you to reference objects from your database project that live inside another namespace (database).

It occurred to me that similar functionality would be incredibly useful for SQL Server Integration Services(SSIS), Analysis Services (SSAS) & Reporting Services (SSRS) projects. After all reports, packages and data source views are rife with references to database objects – why shouldn’t we be able to have design-time dependency checking in our BI projects the same way that database and .Net developers do?

Here are some examples of ways in which this would be useful:

If a SSRS report pulls data from a view, I firstly want to know (at design-time) that that view exists. Secondly, if the view definition changes I want to know that my report will still work.
Similarly for a SSAS cube, if a view referenced in the DSV changes or disappears I want my SSAS project build to fail or succeed accordingly
Similarly for a SSIS Execute SQL Task, if it executes a stored procedure I want to know that the named parameters that I am using actually exist in the stored procedure.

To this end I have submitted three identical suggestions to Connect, one each for SSIS, SSAS & SSRS:

[SSAS] Declare database object dependencies

[SSRS] Declare database object dependencies

[SSIS] Declare database object dependencies

I have said before in my blog post The SQL developer gap that we database and BI developers deserve as much love from Microsoft as our .Net counterparts do and I’m of the opinion that providing design-time dependency checking across the full gamut of BI projects would be a huge step in the right direction. The holy grail is an object dependency graph from database tables all the way up through database views, database functions, stored procedures, DAL, ORM layer & business logic layer all the way through to presentation – I don’t know how long it will take but we will get there one day I am sure, hopefully sooner rather than later!

@JamieT

UPDATE: This feature (i.e. the ability to define dependencies on database objects at build time) is coming to the Entity Framework as confirmed in this Connect submission: http://bit.ly/igmEiS. Let's hope the same comes to SSIS/SSAS/SSRS soon.

It's Official - SQLSaturday is Coming to NYC!

Mike C — Sat, 06 Feb 2010 19:59:00 GMT

New Jersey SQL Server User Group (NJSQL) is bringing SQLSaturday #39 to NYC on April 24, 2010! The free all-day training event will be hosted by Microsoft at their Midtown Manhattan offices. The speaker line-up is growing fast—if you'd like to present, visit the event's open call for speakers. This is a free full-day training event, but registration is required to attend. Seating is limited.

Registration, speaker, and sponsorship details are posted at http://www.sqlsaturday.com/39/eventhome.aspx.

The SQL developer gap (Warning: rant coming up)

jamiet — Tue, 12 Jan 2010 23:43:21 GMT

I recently submitted a bug to Microsoft Connect concerning the behaviour of the expression language in SSRS, if you’re interested you can read about it here: DateAdd() doesn't throw an error when it has invalid parameters.

I got a swift and detailed reply (for which I am grateful) from a fellow on the SSRS team however the content of it wasn’t exactly music to my ears:

While I do agree it would be desirable to have an error here, the SSRS engine makes use of the VB code engine for functions such as this. So, the call to DateAdd is just a passthrough as far as SSRS is concerned. The majority of the functions available in SSRS are actually just VB ones.

In other words the inequities of SSRS’s expression language are down to the frailties of a 14 year old scripting language that should have been thrown out long ago on the coattails of Crystal Reports. Am I the only SQL Server BI developer that feels a little … oh I don’t know … unloved sometimes by the various BI teams in SQL Server land. Let’s have a look at some of the things that we have to put up with:

two different expression languages (one for SSIS, one for SSRS), neither of which support comments as far as I am aware, neither of which have any debugging features and neither of which are extensible
an expression language in SSRS that is based on a dead scripting language and rarely produces meaningful errors
an expression editor in SSIS for which there isn’t even context-sensitive help let alone intellisense
an MDX query editor in SSMS that doesn’t have intellisense
a script task editor in SSIS that shows read-only system variables in the ReadWriteVariables dropdown
I could go on…

None of these issues are particularly prohibitive on their own but when you add them all up (along with many others) I’ve no doubt that we could all be a heck of a lot more productive were they all solved.

I look around at our cousins in .Net land and I see their fancy WPF code editors, extensible languages, Javascript Intellisense, code navigation shortcuts, mockable code, code style checkers, MEF-compliant IDEs, type-inferencing, 3rd-party code editors, keyboard shortcuts, modern type-safe compilers, code generation templates, meaningful error messages, proper debuggers, runtime watches, collapsable code regions, IDEs with built-in refactoring support, built-in code formatting, code documentation tools, whitespace highlighting, code performance analysis tools, LINQ, fluent this-that-and-the-other etc… and I can’t help but feeling a little hard done by. (Anyone that has used Resharper for .Net will know exactly what I mean.) Am I the only SQL guy that feels like a second class citizen in the Microsoft developer ecosystem?

I must be fair and admit that we have it a lot better than other database platform developers (if you have ever used any of the plethora of Oracle developer tools out there you will know what I mean) but nonetheless it would be nice to see a little bit of love go the way of us lowly SQL bods don’t you think?

OK, rant over. My apologies if you came here hoping for some words of wisdom but I’ve been wanting to get this off my chest for ages; normal service will be resumed forthwith!

@Jamiet

P.S. A valid response to this from the SQL Server team may be “submit your ideas to Connect”. I’d like it to be known that the majority of things I have listed above have already been submitted to Connect in some way shape or form and I would be happy to supply a list if one were required!

I should also apologise to the SSRS team for making an example of them – the submission highlighted above is hardly the most annoying of problems listed here but it just happened to be the one that pushed me over the tipping point to writing this!

Start / Stop SQL Server, SSIS, SSAS, SSRS and SQL Server Agent at once with a batch file

jorg — Tue, 06 Jan 2009 21:50:00 GMT

A lot of developers have SQL Server and its different services running on their PC or notebook to develop or test BI solutions. Unfortunately this slows down your system quite a lot. To speed things up when not using SQL Server, I used to stop and start each service manual quite often.

Recently I found out that it's possible to start and stop all services at once with a simple batch file. It now only takes a couple of seconds instead of a few minutes and some annoying steps.

Copy/paste the following in a .txt file and rename it to .bat to make it a batch file, execute it by double clicking the file.

START SCRIPT:

NET START "SQL Server Agent (MsSqlServer)"
NET START "MsSqlServer"
NET START "MsSqlServerOlapService"
NET START "ReportServer"
NET START "SQL Server Integration Services"

STOP SCRIPT:

NET STOP "SQL Server Agent (MsSqlServer)"
NET STOP "MsSqlServer"
NET STOP "MsSqlServerOlapService"
NET STOP "ReportServer"
NET STOP "SQL Server Integration Services"

Webcast on SSRS 2008 and others

RMehta — Thu, 01 May 2008 00:37:00 GMT

Last night (very very late), I attended a live webcast delivered by Peter Myers on SSRS 2008. It was a great introduction to SSRS and the new (some quite refreshing) changes. I continue to be impressed by the power of tablix and of course the dundas charts.I am certainly looking forward to working more with SSRS 2008.

BTW: Jessica Moss and I are delivering a webcast on SSIS Intro next week, but I am more excited about some other upcoming webcasts being delivered by Greg Low, Randy Dyess, Sony Jose and Craig Utley. You can find out about these webcasts and also about the recordings here. Hope to catch you there next week.