output as below

CompanyIDYearRev_IDMetarialID1888574MetarialID1888575MetarialID1888576MetarialID1888577supplier1888574supplier1888575supplier1888576supplier1888577
1039109202133982083.1897.0592.8795.7480.1899.0094.8796.74
1039152202033989880.1810098.8793.7479.1899.0096.8790.74

my result will be

company and year and rev then pivot first Colum based on material id ,pivot second Colum based on material id

with another...

Heh... I love it and had a good laugh.  Thanks, Adi.

Man, you said a mouthful there and I've seen it happen at more...

HI, Here is my issue:

I have 2 SQL 2019 instances and set up 1 linkded server. It works fine in local (remote to the server), but got the error...

You CAN get the date that a user was provided access to a database...

https://docs.microsoft.com/en-us/sql/relational-databases/system-catalog-views/sys-database-principals-transact-sql?view=sql-server-ver15

I could be wrong...

Do you want the output just like what you posted or do you want it in columns?  And, can you clean up what the output is supposed to look like? ...

If you win, send me 5%... 😀

The following will do the trick for you according to your original post.  Thanks for the readily consumable data.

  ...

Just out of curiosity, you do realize that the first query is totally different than the other 2, correct?  And you do realize that leading wild cards for criteria are...

This whole thing is a bit concerning.  Why do you have two databases on the same instance and why have they become different?  There are a couple of slick tricks...

I find it hard to believe that most folks would ever run out of BIGINT values under normal situations.  The field on the other database being a VARCHAR(50) is concerning...

Where I work, the DBA doesn't do the updates.  The infrastructure team does the Windows and SQL Server updates.

We wait a week after they come out and look for the...

It's a funny thing about "drill downs"... I love it when folks drill down to the final layer of 100,000 rows and then wonder what to do.

It is possible to...

Now THAT was an "HR guy" that understood!

A minor optimization on DesNorton's good code would be to remove the ISNULL from the CASE WHEN because a NULL can't be greater than 0 (nor equal to or less...