Viewing 15 posts - 3,106 through 3,120 (of 59,067 total)
I have a quick questions
If I installed Cumulative Update 16 for SQL Server 2019 and then installed GDR 16 for SQL Server 2019 - will I be able to...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 27, 2022 at 6:13 pm
I can't speak for others but relational databases aren't going away. I also love the fact that I don't actually have to write loops in it do to the same...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 27, 2022 at 6:11 pm
Sure I will correct from next by typing the content here and code in code area.
Hi Jeff -I am using third party component which will connect to another third...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 27, 2022 at 5:48 pm
Hi All,
I have a requirement to update set of records to an external environtment which is connected via ADO .net
There are set of records in my table which i...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2022 at 6:49 pm
I don't know what you mean by "Feature Flag". On the SQL side, knowing that is super important. Databases are the proverbial "Center of the Universe". If you don't think...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2022 at 6:45 pm
Was the backup it was trying to copy actually finished? If it wasn't, there's your "sharing violation".
If you try to rename a file to what the current name is and...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2022 at 6:28 pm
I just figured out what line I was getting the error on:
Msg 468, Level 16, State 9, Line 244 Cannot resolve the collation conflict between "Latin1_General_100_BIN2_UTF8" and "SQL_Latin1_General_CP1_CI_AS" in...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2022 at 6:23 pm
I agree... that's a great simplification. But it doesn't return all the rows with the unique number.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2022 at 3:12 pm
I tried this but I got the following err
FUNCTION 'OBJECT_SCHEMA_NAME' is not supported.
You basically said that you were using "Synapse SQL Serverless Pool". There are a lot of things...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2022 at 3:04 pm
MySQL functions --
DATE_SUB(CURDATE(), INTERVAL 7 DAY)-- won't be of much use on SQL Server 2019.
Yeah... that's just spam for an "Assignment writing" service to help people...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2022 at 2:55 pm
Here's the rendition I came up with. It produces the same answer as Phil's. The % of Batch in the Actual Execution Plan says that mine is 27% faster but...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2022 at 2:44 am
Ok... now that I've read the post that I missed, I've added 'P6' to the list of PartNumbers with all '2's for 3 entries to test.
--Add 'P6'...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2022 at 2:02 am
the goal mfrom asking question is to get result above without string aggreagte or comma separated suppose i have
p1 1,2,3
p2 2,2,2
both p1 and p2 both have same count and...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2022 at 1:49 am
I still want to know why the OP wants to avoid the STRING_AGGREGATE() function.
--Jeff Moden
Change is inevitable... Change for the better is not.
July 26, 2022 at 12:20 am
I work with what I consider a large number of third party databases. I still troubleshoot poorly performing queries. I now have DBA acquaintances at those companies and they...
--Jeff Moden
Change is inevitable... Change for the better is not.
July 25, 2022 at 11:46 pm
Viewing 15 posts - 3,106 through 3,120 (of 59,067 total)