July 2, 2015 at 9:10 pm
Personally, I like SSMS. I spend most of my day working in it and rarely close it. I don't use SSIS or the data tools in VS because SSMS does everything I need - it gives me an object explorer and a T-SQL window. Yeah, some of the other stuff is nice, but I don't use the View Designer or Table Designer. In fact, I'd probably disable the View Designer if I could. 😛
July 3, 2015 at 7:45 am
Now if they would just nuke SSIS from orbit. Millions of man hours lost to its quirks...
July 5, 2015 at 3:17 pm
I really enjoy using SSMS with SQL Prompt. I write hundreds of lines of code each day and really will enjoy more focus on making SSMS better for the future.
For report development, I still use Report Builder 3.0 for quick ad-hoc reports even though I do have BIDS. This is obsolete to me because there are too many good reporting solutions available to us that are taking this area by storm. It's only a matter of time before I convert everything I've done in SSRS to either MicroStrategy or Tableau in the next few months.
However, I do wish SSAS got some love. I see huge potential there if they made it better for data mining. But, I think MS has been focusing on Azure ML and other avenues if I'm not mistaken?
July 6, 2015 at 7:19 am
chrisn-585491 (7/3/2015)
Now if they would just nuke SSIS from orbit. Millions of man hours lost to its quirks...
Too bad there is no up vote or something similar, because this post so deserves some up votes!!
July 6, 2015 at 7:25 am
One of the most annoying things about the SSMS shell is the kludgy way you have to go about having multiple queries in the same query tab. You either have to keep them in separate tabs, or highlight the lines of the query you want to run, or comment out the ones you don't.
When I am working on a complex query, I usually start small and work up to the more complex in a very iterative way. SSMS does not make doing that easy.
July 6, 2015 at 7:36 am
abatej (7/6/2015)
One of the most annoying things about the SSMS shell is the kludgy way you have to go about having multiple queries in the same query tab. You either have to keep them in separate tabs, or highlight the lines of the query you want to run, or comment out the ones you don't.When I am working on a complex query, I usually start small and work up to the more complex in a very iterative way. SSMS does not make doing that easy.
It's true that it's not easy, but there are ways and means that are not that troublesome.
I am pretty sure there are addins out there that let you use a certain key press to run the statement where your cursor is currently positioned, but I personally don't like that idea.
What I do is stick a "set noexec on;" at the top of the window, then stick a "set noexec off;" at the bottom.
As each query gets written (and usually for this sort of multi-statement work, it builds another table), I move the "set noexec off;" back to the bottom and start the next query.
This way I can just use F5 to run the "page" and it only actually executes the section(s) I want.
Another benefit of this method is that intellisense still works for any objects built inside the "set noexec on;" <-> "set noexec off;" region.
MM
select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);July 6, 2015 at 8:09 am
chrisn-585491 (7/3/2015)
Now if they would just nuke SSIS from orbit. Millions of man hours lost to its quirks...
Working with SSIS is a lot like hiking through the jungle; simply striking out on your own will be a kludgy adventure. It helps to learn by following existing patterns and practices. I've found the solution to a lot of problems hinges around the use of expressions and sometimes T-SQL tasks; it's definately not all drag and drop.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
July 6, 2015 at 8:36 am
Eric M Russell (7/6/2015)
chrisn-585491 (7/3/2015)
Now if they would just nuke SSIS from orbit. Millions of man hours lost to its quirks...Working with SSIS is a lot like hiking through the jungle; simply striking out on your own will be a kludgy adventure. It helps to learn by following existing patterns and practices. I've found the solution to a lot of problems hinges around the use of expressions and sometimes T-SQL tasks; it's definately not all drag and drop.
I found the secret that works for me is to write it in T-SQL instead. 😀
July 6, 2015 at 12:52 pm
This (SSC) being primarily a community of folks that favor T-SQL I am not surprised at the piling on to SSIS and SSRS on a thread highlighting SSMS :hehe: To me it's a matter of what works and what quirks you're willing to manage to get a particular job done. All this while remaining mindful that not every screw embedded in a business requirement is best bashed in with a T-SQL hammer, however possible it might be.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
February 14, 2017 at 1:40 am
It is amazing how little effort that is often given to tooling that comes with systems. Tools may not be the beating heart of them system but they are an essential organ.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
Viewing 10 posts - 16 through 24 (of 24 total)
You must be logged in to reply to this topic. Login to reply