Please stop posting  the same question over and over.

you were given the answer before on https://www.sqlservercentral.com/forums/topic/the-tabular-view-feature-is-not-included-in-the-64-bit-standard-edition-of - and as you seem not to like the answer please go and read...

• This reply was modified 5 years, 5 months ago by frederico_fonseca.

That's not really the best way to do it as you have multiple "joins" to the same table when you can do it with a single one

try like this

            
April 24, 2020 at 10:00 pm
            
#3746210

            
            
                                                
        

Hi Frederico Fonseca,

Yes, that might change the collation of my database, but not that of TEMPDB. So any query using a #temp table would need to be checked (and...

Henrik - you can change its collation - just not as easy as doing it on Prem

see https://www.mssqltips.com/sqlservertip/5530/how-to-change-an-azure-sql-database-collation/

could you please explain in more detail the layout of your DV with regards to this transaction data, both hub, links and sats - having their DDL including indexes would...

you should have the indexes that are required to support your queries - having them as Columnstore or not will depend on your needs and on your testing that have...

SELECT REPLACE(oldvalue,'*', replicate('0', 12 - len(t.oldvalue) + 1)) newvalue
from (values 
         ('ABC*1')
       ...

• This reply was modified 5 years, 5 months ago by frederico_fonseca.

another one - just weeding out options as not quite sure of what the issue is.

EXEC xp_logininfo 'xxx'

and another option - it is possible that the user is setup on...

• This reply was modified 5 years, 5 months ago by frederico_fonseca.

its now necessarily as you think - just by looking at the image you have tasks running in parallel - maybe it was just timing of when you took the...

the way you have it setup it should execute them in parallel - except potentially the drop of indexes as that locks system tables - but that should be fast...

Test it - easy enough for you to create a table with normal compression and...

you didn't tell us what you mean by "the data returns instantaneously" - if by this you mean it returns to your SSMS grid then do not use this as...

can you give the output of these please.

select containment_desc
from sys.databases 
where name = db_name()

select  type_desc
, is_disabled
, default_database_name

from sys.server_principals
where name =  'xxxx' -- replace with login...

try the following code - without changes other than the login name and give us the output

if (original_login() <> suser_name())
begin
    print 'revert'
  ...

potentially something similar to this

select customerid
     , max(case when [Data Entry] = 'entry' then [Data Entry] else null end) as [Data Entry]
 ...