October 17, 2018 at 10:57 am
Ya, coincidence I guess. I have seen some people bashing TOAD, but there are a lot of things I like about it. This is the first time I have ran into this problem. I will likely continue to use it most of the time and just use SSMS to double check when I see funky results.
October 17, 2018 at 11:05 am
robert.wiglesworth - Wednesday, October 17, 2018 10:57 AMYa, coincidence I guess. I have seen some people bashing TOAD, but there are a lot of things I like about it. This is the first time I have ran into this problem. I will likely continue to use it most of the time and just use SSMS to double check when I see funky results.
In the SQL Server world most people are going to be hesitant to pay for something when SSMS works just fine. Now if you're using other DB's that don't have relatively decent clients included with them there's a lot more reason to use it.
October 17, 2018 at 11:12 am
Well, where I work we have an enterprise license and its just available for anyone who wants to use it. So it doesn't cost anything more than what we are already paying. I started out just trying it out and then got hooked on some of the neat little options it has.
October 17, 2018 at 11:47 am
robert.wiglesworth - Wednesday, October 17, 2018 10:57 AMYa, coincidence I guess. I have seen some people bashing TOAD, but there are a lot of things I like about it. This is the first time I have ran into this problem. I will likely continue to use it most of the time and just use SSMS to double check when I see funky results.
To that end, I worked with Oracle for about 3 years.... TOAD did help a whole lot! To reverse the dig I made, SSMS, especially version 17.x, leaves a whole lot to be desired. They added some great functionality and removed some that has caused me no end of pain.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 17, 2018 at 11:38 pm
robert.wiglesworth - Wednesday, October 17, 2018 9:16 AMOK, so I figured this out. It was in SSIS. I looked at the metadata for the process that was pulling this data and it had dbdate as the data type for that column. It must have carried that from copy and pasting in the query or something. Either way, I edited the data type for that field to dbtimestamp and now everything is working as desired.Thanks for helping me get through this!
Thanks for the feedback on the cause and the fix, Robert.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 18, 2018 at 8:18 am
robert.wiglesworth - Wednesday, October 17, 2018 11:12 AMWell, where I work we have an enterprise license and its just available for anyone who wants to use it. So it doesn't cost anything more than what we are already paying. I started out just trying it out and then got hooked on some of the neat little options it has.
And speaking of options, last time I saw Toad (in an Oracle shop), it had all kinds of "options", so I wonder if perhaps one of those options caused the problem?
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
Viewing 6 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply