We always use

-- switch sqlserver logfiles (errorlogs)
EXEC msdb.dbo.sp_cycle_errorlog 

and

EXEC msdb.dbo.sp_cycle_agent_errorlog;

We do this in a single SQLAgent job, but in 2 steps, configured so they...

What disturbs me more is the fact that "will never share information" gets thrown overboard.

MS baught Whatsapp for its technology.

Instead of rebranding it to MSwhatever, they opt to keep the...

• This reply was modified 4 years, 10 months ago by Johan Bijnens.

keep min mind, a disabled job can still be fired using sp_start_job !

( it will just not be started by its coupled schedules or alerts )

Just in case you let...

• This reply was modified 4 years, 10 months ago by Johan Bijnens.

Nice article !

Check https://cloudblogs.microsoft.com/dynamics365/no-audience/2015/01/16/using-sql-server-extended-events-to-produce-a-blocked-process-report/

What have you tried ?

hierarcyId may have looked to be an interesting option, but ....

https://www.sqlservercentral.com/articles/hierarchies-on-steroids-1-convert-an-adjacency-list-to-nested-sets

https://www.sqlservercentral.com/articles/hierarchies-on-steroids-2-a-replacement-for-nested-sets-calculations-1

here is a nice ref:

by Brent Ozar

https://www.brentozar.com/archive/2020/10/want-to-use-columnstore-indexes-take-the-columnscore-test/

or direct https://columnscore.com/

Spot on, Jeff ! ??

Oh BTW, On top of compression, you may also want to fiddle around with following settings to see what works best for you !

--Media Set Options
 ...

This may be a start

;With cteSel as (
Select cUser, dDate, rank() over ( partition by cUser Order by cUser, dDate desc) UserDateRank
from #tmp_UserDates
) 
Select distinct *
from cteSel
where...

Compressed backups are available on every edition except Express Edition  !...

SSMS-Setup-ENU.18.8.exe /Passive DoNotInstallAzureDataStudio=1 /install /quiet /norestart /log SSMS_install.log

ref: last line of this paragraph

• This reply was modified 5 years ago by Johan Bijnens.

Did you try

select convert(decimal(22,2), Case when Sum(@q *COALESCE(NULLIF(COALESCE(@Weight, 0), 0), 0.01)) < 0.01 then 0.01
else Sum(@q *COALESCE(NULLIF(COALESCE(@Weight, 0), 0), 0.01)) 
end )

That is a concern you should have expressed during the interview.

If you want it to be interpreted correctly ... ask your MS representative.

• This reply was modified 5 years ago by Johan Bijnens.