Viewing 15 posts - 3,811 through 3,825 (of 59,067 total)
Awesome! Thank you for the feedback. No need to reply to my question about code on StackOverFlow. I just found out they deleted a super important post that leads to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2022 at 9:12 pm
I used powershell to create a script that prepares the files for bulk insert. it ensures that the columns match with the destination table. works beautifully.
You mean...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2022 at 8:41 pm
There's no place with long term historical lock information that I know of (unless you've kept every transaction log backup). You can, however, start to collect current lock information. One...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2022 at 8:16 pm
It would be helpful if you posted the CREATE TABLE statement for the table that contains the data and any rows where the code you've used isn't working. And, to...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2022 at 7:28 pm
If the absence of locking errors is evidence, then perhaps just going through the SQL Error logs from before the change and after the change would be what you need.
The...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2022 at 7:09 pm
Duplicates involves all columns. I would like to add an index column to identify each row.
If that's the case, then perhaps create a persisted computed consisting of a formula...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2022 at 6:24 pm
First i would like to able to have an unique identifier. Is the unique index the way to go?
Would you answer my question about the dupes, please? And, if...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2022 at 4:58 pm
Sure. Your join condition is as follows...
ON nr.AcceptedValuesOptionID = m.ShelfLifeConditin
Do you have indexes on both of those columns? Probably not especially since one of the tables is...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 3, 2022 at 12:02 am
Just to be sure, you didn't upset anyone. I'm just amazed that people don't do more on their posts to help others actually know enough to help them. For future...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2022 at 11:00 pm
It currently looks like a "dupe" involves all of the columns that you posted. Is that correct?
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2022 at 7:33 pm
Try running an "Estimated Execution plan on that". I'm thinking that the join condition is inadequate and has caused a huge and terrible CROSS JOIN.
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2022 at 6:37 pm
Hope I caught all replies, I'm going with having ORM fix code as suggested..
You didn't. And while I agree that ORM code frequently needs to be fixed, it's probably...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2022 at 6:11 pm
Even after participating in forums for more than 2 decades I guess I'll never understand why people post and then never answer a simple question asking a a small example...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2022 at 6:02 pm
You are probably right Jeff, the actual use case is to log specific query executions to a table...but now you've got me thinking of other potential ways...🤔
It's partly for...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2022 at 5:25 pm
It would be really helpful if you could include an ACTUAL Execution Plan (as opposed to an Estimated Execution Plan). See the article at the second link in my signature...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 2, 2022 at 5:20 pm
Viewing 15 posts - 3,811 through 3,825 (of 59,067 total)