Viewing 15 posts - 1,516 through 1,530 (of 59,067 total)
Did you previously try Grant Fritchey's solution at your previous very similar post?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 28, 2023 at 12:19 pm
This will sound a bit stupid or as a shot in the dark but, when you select @@ServerName, does it return the instance name or something else?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2023 at 6:00 pm
You could also try sjones@sqlservercentral.com (Steve Jones...the editor).
--Jeff Moden
Change is inevitable... Change for the better is not.
April 27, 2023 at 5:24 pm
Contact WebMaster@SQLServerCentral.com and let them know. They sometimes miss things.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2023 at 8:35 pm
Sorry for my slow reply.
I created the user from login. At the server and database level they are only in the public role and I can't see anything relevant...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 26, 2023 at 8:32 pm
Here is a different approach.
Niiiicccceee! I'm going to do some performance tests there because, although it's not a super common request, it's a request that has happened often enough...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2023 at 6:02 pm
The prompt was based on minimal code
this sql code omits a 2nd column with which we could order the rows. Could you add a date...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2023 at 2:41 am
@richard-2... this is one of the problems with not providing data in a readily consumable test table... everyone make up their own mind as to what the column names and...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2023 at 2:39 am
I think the way to do this is to eliminate dupes while maintaining the order. Then the Lead/Lag comparison of the difference between the previous point goes from positive and...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2023 at 12:35 am
p.s. I'm thinking that your good shot at it needs (as you imply) a little tweaking. Try using the following data and see what I mean...
from (values (3),(10),(9),(8),(8),(8),(11),(12),(13),(12),(11),(6),(3),(2)) v(n)
Results:
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2023 at 12:24 am
Thanks ChatGPT for fixing the data.
interesting. What prompt did you use for that, Steve? I'm always curious.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 25, 2023 at 12:14 am
While answer 3 may meet the overt requirements, it' returns the following "extra" info in the presence of NULL values, as well.
Warning: Null value is eliminated by...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 24, 2023 at 3:07 pm
Sometimes having dates, or parts of dates, as integers work well. But not often. A dimension can make sense, but in most transactional tables, I think dates ought to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2023 at 12:44 am
Calendar and Clock tables make life a lot easier when used as part of a Dimensional model. Especially if it is implemented in a column store.
If you've seen the...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 22, 2023 at 12:43 am
p.s. You should also post the CREATE TABLE code for the table, its keys, and the indexes so we can see if you have possibilities going on such as "Trapped...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 19, 2023 at 5:41 pm
Viewing 15 posts - 1,516 through 1,530 (of 59,067 total)