October 6, 2017 at 5:08 am
Hi all
Predominantly on SQL 2008r2 and SSRS 2008 here with 2012 and 2014 too so I'm already using SSMS 2014
Quick question: I'm having to replace my laptop and just wondering if it's worth using SSDT for designing SSRS reports (and a tiny amount of SSIS) instead of BIDS 2008.
Our "General use" SQL server/SSRS server will be migrated to 2014 shortly but is still currently on 2008r2.
I have installed SSDT on the new laptop and am revolted by the downright awful UI - I'm not change averse per-se but my god it's awful!
If there is significantly improved functionality, or will be when the SSRS is migrated to 2014, I will suck it up and use it, if not I'd rather use BIDS 2008. If anyone is experienced in both and could just give me a "yes it's worth it" or "no, it's just a different type of shiny" I'd be grateful please.
"Knowledge is of two kinds. We know a subject ourselves, or we know where we can find information upon it. When we enquire into any subject, the first thing we have to do is to know what books have treated of it. This leads us to look at catalogues, and at the backs of books in libraries."
— Samuel Johnson
I wonder, would the great Samuel Johnson have replaced that with "GIYF" now?
October 6, 2017 at 5:47 am
If you're connecting to SQL Server 2008 then SSDT is not compatible. You have to use BIDS with SSRS/SSIS/etc 2008. SSDT 2017/2016 is compatible with SQL Server 2012 onwards. Conversely you cannot use BIDS with SQL Server 2012 onwards (you need to use SSDT 2012 onwards, with 2016 being the first that is back compatible).
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
October 6, 2017 at 6:06 am
Thanks for the reply Thom.
In what way(s) is it incompatible? I took a copy of one of my current 2008 BIDS projects, migrated it to SSDT and all seemed OK (this was a very quick and dirty check).
I could use existing 2008 DataSources, could create a quick, basic report from the wizard and was able to deploy to the 2008r2 server and run the report.
I have to say that all the dialogues seemed identical to BIDS, it's just the main window that is repulsive 🙂
I think I will stick with BIDS anyway, until I am forced to switch - either for compatibility or some compelling new feature/tool.
Cheers
David
"Knowledge is of two kinds. We know a subject ourselves, or we know where we can find information upon it. When we enquire into any subject, the first thing we have to do is to know what books have treated of it. This leads us to look at catalogues, and at the backs of books in libraries."
— Samuel Johnson
I wonder, would the great Samuel Johnson have replaced that with "GIYF" now?
October 6, 2017 at 6:31 am
SSDT cannot deploy to SQL Server 2008. If you've done a one way upgrade on your project, and not kept a backup, you have problem, as you won't be able to deploy to 2008 without remaking your project, and possibly packages.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
October 6, 2017 at 7:35 am
Yep, took a copy, did the one way upgrade and worked on that 😉 after what you said, I wanted to see what happened using a SSDT project and keeping everything else the same, including deployment location.
I certainly didn't have any problems deploying the single new report I created in the project to, or running it on, the 2008r2, granted it was only a quick test.
When I get a bit more time, I will create a whole new project in SSDT and try deploying to 2008, I'm interested to see what happens now 🙂
"Knowledge is of two kinds. We know a subject ourselves, or we know where we can find information upon it. When we enquire into any subject, the first thing we have to do is to know what books have treated of it. This leads us to look at catalogues, and at the backs of books in libraries."
— Samuel Johnson
I wonder, would the great Samuel Johnson have replaced that with "GIYF" now?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply