June 20, 2017 at 4:33 pm
Ed Wagner - Tuesday, June 20, 2017 4:07 PMSean Lange - Tuesday, June 20, 2017 1:23 PMSteve Jones - SSC Editor - Tuesday, June 20, 2017 12:37 PMSean Lange - Tuesday, June 20, 2017 12:16 PMBeing a keyboard guy I prefer this but honestly either one is a huge time saver. Gosh I feel so embarrassed I didn't know this was possible.
Don't be. It came in VS, and I learned it years ago (2010? 2012?), but forgot. I had to look it up, but not I'll use it to move commas periodically and then remember it. It feels more useful in C# than T-SQL, but maybe that's me.
As a dotnet guy I feel I should have known this. I have actually used this trick about 7-8 times already in t-sql within the last couple hours.
Does it sound weird that I learned it in SSMS before even trying it in .NET? 😉
I learned about it this year. Before learning it I would copy and paste between SSMS and UltraEdit where I would use the column editing feature in UltraEdit to accomplish what I needed.
June 20, 2017 at 5:23 pm
Lynn Pettis - Tuesday, June 20, 2017 4:33 PMEd Wagner - Tuesday, June 20, 2017 4:07 PMSean Lange - Tuesday, June 20, 2017 1:23 PMSteve Jones - SSC Editor - Tuesday, June 20, 2017 12:37 PMSean Lange - Tuesday, June 20, 2017 12:16 PMBeing a keyboard guy I prefer this but honestly either one is a huge time saver. Gosh I feel so embarrassed I didn't know this was possible.
Don't be. It came in VS, and I learned it years ago (2010? 2012?), but forgot. I had to look it up, but not I'll use it to move commas periodically and then remember it. It feels more useful in C# than T-SQL, but maybe that's me.
As a dotnet guy I feel I should have known this. I have actually used this trick about 7-8 times already in t-sql within the last couple hours.
Does it sound weird that I learned it in SSMS before even trying it in .NET? 😉
I learned about it this year. Before learning it I would copy and paste between SSMS and UltraEdit where I would use the column editing feature in UltraEdit to accomplish what I needed.
Ah yes, you're another UltraEdit user. It might be from getting accustomed to it over the years, but I find it to be such a handy tool to have. Even with the maturity of SSMS, I still find UltraEdit great for some find/replace stuff.
June 21, 2017 at 1:48 am
Ed Wagner - Tuesday, June 20, 2017 4:07 PMSean Lange - Tuesday, June 20, 2017 1:23 PMSteve Jones - SSC Editor - Tuesday, June 20, 2017 12:37 PMSean Lange - Tuesday, June 20, 2017 12:16 PMBeing a keyboard guy I prefer this but honestly either one is a huge time saver. Gosh I feel so embarrassed I didn't know this was possible.
Don't be. It came in VS, and I learned it years ago (2010? 2012?), but forgot. I had to look it up, but not I'll use it to move commas periodically and then remember it. It feels more useful in C# than T-SQL, but maybe that's me.
As a dotnet guy I feel I should have known this. I have actually used this trick about 7-8 times already in t-sql within the last couple hours.
Does it sound weird that I learned it in SSMS before even trying it in .NET? 😉
Can't believe I didn't know about this either. This is honestly going to make my day so much easier today...
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
June 21, 2017 at 7:02 am
Ed Wagner - Tuesday, June 20, 2017 4:07 PMSean Lange - Tuesday, June 20, 2017 1:23 PMSteve Jones - SSC Editor - Tuesday, June 20, 2017 12:37 PMSean Lange - Tuesday, June 20, 2017 12:16 PMBeing a keyboard guy I prefer this but honestly either one is a huge time saver. Gosh I feel so embarrassed I didn't know this was possible.
Don't be. It came in VS, and I learned it years ago (2010? 2012?), but forgot. I had to look it up, but not I'll use it to move commas periodically and then remember it. It feels more useful in C# than T-SQL, but maybe that's me.
As a dotnet guy I feel I should have known this. I have actually used this trick about 7-8 times already in t-sql within the last couple hours.
Does it sound weird that I learned it in SSMS before even trying it in .NET? 😉
Nope. Sounds like what just happened to me too.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
June 21, 2017 at 8:54 am
GAAAAAAAAAAAAAHHHHHHHHHHH. So annoyed. Spent several minutes writing up a post for the Programming General forum about an SSIS script task problem I had a few weeks ago. But I couldn't remember the error I was getting, so I went into SSIS and executed just that task to get it...
And now the damn thing works.
<headdesk>
Why oh why does the broken thing not break when I need it to break?
June 21, 2017 at 9:02 am
Brandie Tarvin - Wednesday, June 21, 2017 8:54 AMGAAAAAAAAAAAAAHHHHHHHHHHH. So annoyed. Spent several minutes writing up a post for the Programming General forum about an SSIS script task problem I had a few weeks ago. But I couldn't remember the error I was getting, so I went into SSIS and executed just that task to get it...And now the damn thing works.
<headdesk>
Why oh why does the broken thing not break when I need it to break?
Heh - it sounds like a household appliance. The only time they don't screw up is when the repairman is present and ready to fix it. 😛
June 21, 2017 at 9:42 am
This is totally off topic but man I really hate contract developers sometimes. We had this guy in our shop for about three months helping relieve some of the pressure with some major projects. He took over one of our asp.net sites and was really proud of all the "improvements" he made. He used some automated tool to enforce some arbitrary naming conventions. He was so excited because he got the compile time down by a minute or so for the entire site. Now this site is built with modules and there are over 100 modules for this site. In the several years since I first created it we have NEVER compiled every module at one time. That is kind of the point of modules, you get to compile and deploy only the parts that need changed.
The worst thing is that his tool decided to change property names from ID to Id. This to me is quite silly. I personally prefer ID but it is really a matter of preference, why change code that is already working. And of course his tool didn't fix things like setting the KeyColumn on databound objects so all of those were broken. We also use reflection in some factories to map object properties so we don't have to map them by hand. This was recently another problem because one piece of the code is looking at the column names in the database to map to properties. Since our database AND dotnet are case sensitive Id <> ID. I have spent the last three hours chasing down why a library I wrote 5 years ago is suddenly failing where it is has worked perfectly since day one. In fact, in source control this file had only 1 entry in the history prior to this guy.
UGH!!! Sorry needed to vent. Glad that guy isn't here anymore or I would have run out of porkchops by now.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
June 21, 2017 at 9:46 am
Sean Lange - Wednesday, June 21, 2017 9:42 AMThis is totally off topic but man I really hate contract developers sometimes. We had this guy in our shop for about three months helping relieve some of the pressure with some major projects. He took over one of our asp.net sites and was really proud of all the "improvements" he made. He used some automated tool to enforce some arbitrary naming conventions. He was so excited because he got the compile time down by a minute or so for the entire site. Now this site is built with modules and there are over 100 modules for this site. In the several years since I first created it we have NEVER compiled every module at one time. That is kind of the point of modules, you get to compile and deploy only the parts that need changed.The worst thing is that his tool decided to change property names from ID to Id. This to me is quite silly. I personally prefer ID but it is really a matter of preference, why change code that is already working. And of course his tool didn't fix things like setting the KeyColumn on databound objects so all of those were broken. We also use reflection in some factories to map object properties so we don't have to map them by hand. This was recently another problem because one piece of the code is looking at the column names in the database to map to properties. Since our database AND dotnet are case sensitive Id <> ID. I have spent the last three hours chasing down why a library I wrote 5 years ago is suddenly failing where it is has worked perfectly since day one. In fact, in source control this file had only 1 entry in the history prior to this guy.
UGH!!! Sorry needed to vent. Glad that guy isn't here anymore or I would have run out of porkchops by now.
Actually, it's a shame the guy's not there anymore. Otherwise you could perhaps get him to change stuff back on his own time. After all, he did something he wasn't commissioned to do, and that broke your stuff, so he should be commissioned to repair it.
June 21, 2017 at 9:51 am
Hugo Kornelis - Wednesday, June 21, 2017 9:46 AMSean Lange - Wednesday, June 21, 2017 9:42 AMThis is totally off topic but man I really hate contract developers sometimes. We had this guy in our shop for about three months helping relieve some of the pressure with some major projects. He took over one of our asp.net sites and was really proud of all the "improvements" he made. He used some automated tool to enforce some arbitrary naming conventions. He was so excited because he got the compile time down by a minute or so for the entire site. Now this site is built with modules and there are over 100 modules for this site. In the several years since I first created it we have NEVER compiled every module at one time. That is kind of the point of modules, you get to compile and deploy only the parts that need changed.The worst thing is that his tool decided to change property names from ID to Id. This to me is quite silly. I personally prefer ID but it is really a matter of preference, why change code that is already working. And of course his tool didn't fix things like setting the KeyColumn on databound objects so all of those were broken. We also use reflection in some factories to map object properties so we don't have to map them by hand. This was recently another problem because one piece of the code is looking at the column names in the database to map to properties. Since our database AND dotnet are case sensitive Id <> ID. I have spent the last three hours chasing down why a library I wrote 5 years ago is suddenly failing where it is has worked perfectly since day one. In fact, in source control this file had only 1 entry in the history prior to this guy.
UGH!!! Sorry needed to vent. Glad that guy isn't here anymore or I would have run out of porkchops by now.
Actually, it's a shame the guy's not there anymore. Otherwise you could perhaps get him to change stuff back on his own time. After all, he did something he wasn't commissioned to do, and that broke your stuff, so he should be commissioned to repair it.
Good point. I have spent a fair amount of time fixing his "fixes".
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
June 21, 2017 at 9:55 am
Ed Wagner - Wednesday, June 21, 2017 9:02 AMBrandie Tarvin - Wednesday, June 21, 2017 8:54 AMGAAAAAAAAAAAAAHHHHHHHHHHH. So annoyed. Spent several minutes writing up a post for the Programming General forum about an SSIS script task problem I had a few weeks ago. But I couldn't remember the error I was getting, so I went into SSIS and executed just that task to get it...And now the damn thing works.
<headdesk>
Why oh why does the broken thing not break when I need it to break?
Heh - it sounds like a household appliance. The only time they don't screw up is when the repairman is present and ready to fix it. 😛
Have you noticed how this only ever happens when there's a really high non-refundable call-out charge?
For fast, accurate and documented assistance in answering your questions, please read this article.
Understanding and using APPLY, (I) and (II) Paul White
Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden
June 21, 2017 at 10:28 am
Sounds like a day to rant about problems...
Just migrated a customer from SQL2012 / Server 2008R2 to a new server, SQL2014 / Server 2012. Seemed to go swimmingly and I'm having visions of one less server to deal with.
Until today.
Customer reports one of their jobs on the new server is failing. Job executes an SSIS package that reads data from an Excel file (xlsx) on a network share. Access to the share is granted to the SSIS proxy account, the same one from the old server. Look in the execution history (I love the SSIS Catalog logging) and it's complaining about the ACE OLE.DB driver. Huh, I thought I loaded that when I stood the server up, take a look in Linked Server providers and there it is. Check the old server, it's *not* in the Linked Server providers? WTH? OK, so what's causing this and why and how did it work on the old server?
Do more digging, poking around, find a forum post elsewhere on checking if you've got the 32-bit or 64-bit ACE driver. Turns out, the old server has the 32-bit, the new has the 64-bit (both on 64-bit OSes and SQL)
So now I'm getting ready to try removing the provider on the QA server (yeah, turns out the customer never tried this job in QA, or any others...) and installing the 32-bit. If that fixes it, then it's one more thing on my to-do list for Saturday when I'm loading the OS patches...
June 21, 2017 at 10:32 am
Sean Lange - Wednesday, June 21, 2017 9:42 AMThis is totally off topic but man I really hate contract developers sometimes.
Good thing that starting this week I'm no longer a contractor but a FTE. 😀
June 21, 2017 at 10:55 am
Luis Cazares - Wednesday, June 21, 2017 10:32 AMSean Lange - Wednesday, June 21, 2017 9:42 AMThis is totally off topic but man I really hate contract developers sometimes.Good thing that starting this week I'm no longer a contractor but a FTE. 😀
Well, if you miss it, just let us know. We can treat you like a contractor any time. @=)
June 21, 2017 at 11:43 am
ChrisM@Work - Wednesday, June 21, 2017 9:55 AMEd Wagner - Wednesday, June 21, 2017 9:02 AMBrandie Tarvin - Wednesday, June 21, 2017 8:54 AMGAAAAAAAAAAAAAHHHHHHHHHHH. So annoyed. Spent several minutes writing up a post for the Programming General forum about an SSIS script task problem I had a few weeks ago. But I couldn't remember the error I was getting, so I went into SSIS and executed just that task to get it...And now the damn thing works.
<headdesk>
Why oh why does the broken thing not break when I need it to break?
Heh - it sounds like a household appliance. The only time they don't screw up is when the repairman is present and ready to fix it. 😛
Have you noticed how this only ever happens when there's a really high non-refundable call-out charge?
Wait...you mean you know of a case where there is a refundable service charge??? I've never heard of such a thing.
June 21, 2017 at 11:45 am
Luis Cazares - Wednesday, June 21, 2017 10:32 AMSean Lange - Wednesday, June 21, 2017 9:42 AMThis is totally off topic but man I really hate contract developers sometimes.Good thing that starting this week I'm no longer a contractor but a FTE. 😀
Well, congratulations Luis. Well done. Are you still in Atlanta? Just as importantly, do you enjoy it, both the job and area?
Viewing 15 posts - 58,966 through 58,980 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply