November 9, 2013 at 5:27 pm
arnipetursson (11/8/2013)
A talk about how to determine the right tool for the job.
Very cool. I'll start with a bit of a play on words. "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." 😛
What we often see is that features can get overused because they make the coding easy (e.g. table variables, CTEs) but they may have unforseen consequences.
What are some newer examples of this kind of thing?
POWERSHELL.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 9, 2013 at 10:17 pm
Our budget at work is very tight. No money for any conferences nor any training. The possibilities of lay offs are very real. Last year we had our first SQL Saturday; the only training I'll get this year is another SQL Saturday, if we have one, plus what I can learn online.
Rod
November 11, 2013 at 9:05 am
Jeff Moden (11/9/2013)
arnipetursson (11/8/2013)
A talk about how to determine the right tool for the job.Very cool. I'll start with a bit of a play on words. "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." 😛
Very similar to my mantra (different meaning of course): "Just because you CAN do something in T-SQL, doesn't mean it's a good idea!"
I have to disagree with you on Powershell though.
Because of issues with SCOM, I created a whole suite of powershell scripts for my monitoring and admin needs.
Allowed me to have a single set of scripts that I run from one place, and all I have to do when i set up a new server is add it to my server list tables and set up the login that runs the scripts.
Now I am even monitoring AWS MySQL instances with my scripts.
This is very similar to what i used to do with shell and perl in my previous life as a Sybase DBA.
The one gotcha I have come across with powershell is memory issues, particularly related with how it reads files.
November 11, 2013 at 9:42 am
arnipetursson (11/11/2013)
Jeff Moden (11/9/2013)
arnipetursson (11/8/2013)
A talk about how to determine the right tool for the job.Very cool. I'll start with a bit of a play on words. "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." 😛
Very similar to my mantra (different meaning of course): "Just because you CAN do something in T-SQL, doesn't mean it's a good idea!"
I have to disagree with you on Powershell though.
Because of issues with SCOM, I created a whole suite of powershell scripts for my monitoring and admin needs.
Allowed me to have a single set of scripts that I run from one place, and all I have to do when i set up a new server is add it to my server list tables and set up the login that runs the scripts.
Now I am even monitoring AWS MySQL instances with my scripts.
This is very similar to what i used to do with shell and perl in my previous life as a Sybase DBA.
The one gotcha I have come across with powershell is memory issues, particularly related with how it reads files.
I'm not suggesting that Powershell is a bad thing. Even I use it.
My response was because someone asked if something else had been abused like Recursive CTEs, Cursors, CLR, etc and the answer is "Yes"... like any shiney new object in SQL Server, Powershell has been seriously abused/misused. Most of the people that are doing the abusing seem to be those who know how to program and not much about SQL Server. There are a couple that do know SQL Server quite well but insist on doing simple things using Powershell just because they can.
--Jeff Moden
Change is inevitable... Change for the better is not.
November 11, 2013 at 3:19 pm
How to deal with Entity Framework (and the like) as a DBA. Performance fixing especially.
November 13, 2013 at 11:50 am
One of the areas I have been exploring is Sharepoint integration and SQL Server. Sharepoint is here to stay, and the quicker you get up to speed on it the better prepared you will be as a DBA.:-D
"Technology is a weird thing. It brings you great gifts with one hand, and it stabs you in the back with the other. ...:-D"
November 18, 2013 at 3:10 pm
I'd like to learn more about SSIS.
I've gone through the tutorials, but they just barely get you started.
Most of my learning has been trial and error, with lots of trials and lots of errors.
A couple specific things I'd like to know more about
- Best practices for logging
- How best to integrate with TFS
- Understanding the output when you run the package directly.
If anyone has suggestions on books or on-line sources that have helped them, I'd appreciate it.
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply