Viewing 15 posts - 331 through 345 (of 59,063 total)
There should be an additional lesson learned here... when doing modifications to rows, start with BEGIN TRANSACTION and then run the UPDATE. If the rowcount is right, then COMMIT else...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 31, 2024 at 12:08 am
You can have a look at sys.dm_db_index_usage_stats() to see if there have been any reads or writes since the last time the SQL Server Service was started.
Once you've decided that...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 30, 2024 at 11:58 pm
Hello everyone,
I need your help. I have a “datetime” column (data type is Varchar(64) )with the following content: Sun Sep 29 2024 09:28:55 GMT+0000 (Coordinated Universal Time)
I would...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 30, 2024 at 11:55 pm
Try this... notice the only change is a couple of left outer join's for the drivers table (the word OUTER is optional... I left it out). I not only did...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 30, 2024 at 12:08 am
First, thank you for helping us help you by posting the readily consumable data code.
Ed B.'s code is good, although I'll never use PIVOT because of the issue he pointed...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2024 at 11:48 pm
Thanks for this. It confirms my googling explroations, and I'm about to try it.
I wonder what will happen on those requests where a driver hasn't yet been allocated. They...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2024 at 8:50 pm
It turns out that I simply misread the dd/mm/yyyy format of the expected answer and the original code that I posted was just fine. Here's that post again...
Apparently, you didn't...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2024 at 6:16 pm
Sorry... made a mistake... will repost in, hopefully, a couple of minutes.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2024 at 6:07 pm
Sorry... made a mistake... will repost in, hopefully, a couple of minutes.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2024 at 6:04 pm
Put the same table in the FROM clause twice using a JOIN. The key will be to give each instance of the table a different alias... one called "Driver" and...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2024 at 5:16 pm
I'd also have a meeting with the 3rd party creators of the software and ask them to fix it.
As a bit of a sidebar, this is one of the many...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2024 at 5:08 pm
As Phil suggests, please provide the data in a readily consumable format instead of a graphic to help us help you. See the first link in my signature line below...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2024 at 5:04 pm
I use those tools as a starting point for investigation and not as the truth. Many times the end result of an investigation is modifying an existing index instead...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2024 at 6:09 pm
I'm going to advise some good caution here. There are a ton of tools, including but not limited to SQL Server's built-in "missing indexes" tool but you should never just...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2024 at 2:04 pm
I'm struggling with one thing: dbo.DelimitedSplit8K. What is this?
You can get the code for it in the "Resources" section at the following article, which explains how it works, as...
--Jeff Moden
Change is inevitable... Change for the better is not.
October 24, 2024 at 1:45 pm
Viewing 15 posts - 331 through 345 (of 59,063 total)