Viewing 15 posts - 6,781 through 6,795 (of 59,091 total)
... and it also comes up with correct answers.
(As Brian admitted in a later post) my solution did provide the correct answers!
It's definitely on the right track and does...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2020 at 1:07 pm
Ah... bugger. I thought one of Steve's submittals worked just as well but it misses correct output on some of the items I had in my test table and so...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2020 at 12:47 pm
Just to be sure, are you trying to convert Oracle to SQL Server?
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2020 at 12:46 am
Heh... this is why I hate tests. While I knew the correct answer you were expecting, it's not actually the correct answer. It can be done through a stored procedure...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2020 at 12:25 am
Since you aren't actually using the count for anything other than measuring if the count is greater than "0", just do a check for existence instead of a count... that'll...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 17, 2020 at 12:19 am
I'll get quite a bit of argument from a lot of folks but I've found that REORGANIZE frequently does NOT do a very good job at fixing page density problems...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2020 at 11:40 pm
Totally agreed on the Modified_By and Created_By columns being fix length like an INT column with an FK but, if an application has a generic login, that would mean that...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2020 at 11:17 pm
Hi Jeff, the DBA does not allow me the permission to create/use tally function. Can you provide a solution without using it please?
I wasn't suggesting that YOU create the...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2020 at 6:42 pm
It's (a separate table) is a better practice for multiple reasons especially if it can't be altered without all hell breaking loose. The 4 columns you speak of (I refer...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2020 at 4:04 pm
Nah... it's easier than that. Create a stored procedure that does the work, give the spreadsheet user privs to execute it, and have them execute the stored procedure...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2020 at 2:28 pm
Erased my post... I found an exception to the code I was going to post.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2020 at 6:46 am
This is a triplicated post and multiple solutions have been provided. Please... no posts here. Instead, see the following post where all the other answers are...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2020 at 6:39 am
Thanks, this is ECM Opentext software database server, I did not manage it until today I found the alerts. Asked their team they said some contractors are loading some...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2020 at 6:36 am
p.s. SQL <> SQL so always identify which RDBMS engine you're using.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2020 at 6:30 am
Nah... it's easier than that. Create a stored procedure that does the work, give the spreadsheet user privs to execute it, and have them execute the stored procedure from their...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 16, 2020 at 6:28 am
Viewing 15 posts - 6,781 through 6,795 (of 59,091 total)