Can anyone help me what happen why I can't disable CDC
Shown picture above is two list of CDC I want to disable.
and this screenshot prove that this CDC is still in system
Related
Two years ago a SQL expert opened a SSMS and showed all queries as they were happening in real time. That way he saw which SQL statements were running fast and which took some time to be ran. I remember the queries to be displayed in a "CMD" look alike window. I can't remember if new queries were displayed at the top or were they shown at the bottom of the window.
For the past month I have been trying to figure out how he got this working. I looked everywhere in monitor, but I can't find anything similar to what he showed me than.
The results were similar to the "claymore eth miner window" ...
Can someone point me in the direction of getting this?
You can use sp_whoisactive to get the current running queries. It is very useful to see if currently there is blocking, locking, long running statements.
In order to get better picture of what was going on in the past, you can enable the Query Store. There are some predefined reports:
and various statistics and it is user friendly:
Can we manage Debug levels in Salesforce?
Delete or Edit or at least Rename existing debug level?
I have created a new debug level but missed something and now would like to either change levels to what I need, delete it and create a new one, or rename it to JUNK_whatever and create a new one.
Neither of these options seems to be available. Maybe I simply didn't find it?
P.S. I don't currently have any user trace flags or debug logs.
Thank you!
Yes, you can edit and delete DebugLevels.
From UI perhaps easiest is to use the Developer Console (upper right corner, gear/cog icon). Debug -> Change Log Levels -> Add/Change. Highlight (click) the row you want and remove. It's bit finnicky but it works.
.
You can do it from setup too but I think it shows up only in Classic interface. Switch and type "debug levels" or try https://{my domain here}.my.salesforce.com/7dl
Last but not least you could fire a Tooling API query on the table and then it's a HTTP DELETE request sent to v55.0/tooling/composite/sobjects?ids=recordId. You may need Postman, SoapUI or Workbench for that.
I've set logReplayEvents to false even though that's the default just to be sure but I'm still seeing multiple entries for my orchestration function for a single invocation in the Monitor section on the Azure portal:
Any idea how, if it's possible, I can change this so it just shows one.
I hope you have set LogReplayEvents to false under 'durableTask' key (i.e., disabled emitting verbose orchestration replay events) in the host.json file.
And yeah, by default all non-replay tracking events are emitted.
Perhaps I am missing something but looking at the screenshot provided by you, I cannot really figure out that those logs are related to replay events. That's fine if you have checked each event and found that they are replay event, or else can you go to your App Insights and run below query to see if any replay events are present or not.
traces| extend isReplay = tobool(tolower(customDimensions["prop__isReplay"]))| where isReplay == "True"
Hope this helps at least up to some extend!! Cheers!! :)
We are seeing some issues with our indexer throwing an error every other time it tries to run the indexer on our data-source. Our indexer runs on a schedule and we have Sql server "Change Tracking" turned ON for db and the table that we use for indexing. The indexer runs successfully every other time which is strange. I will attach a picture to show you the indexer status page. The odd thing is it shows an error saying:
"Indexing was stopped because the data source has no change detection policy and corresponding quota of 100000 documents has been reached. To index more documents please add a change detection policy".
So like I mentioned we have the "Change detection policy" set (Change Tracking is ON) and indexer running on a schedule. And it works every other time. We are on a "standard" billing tier so we do not have a quota "100000". We believe that this error might also be contributing to our counts in the index data-source and index table not to match. The indexer is NOT deleting the ID that have been removed from our source table.
I have attached an image to show the status page of our indexer. Please help! We have launched our search and are seeing issues pretty late in the game.
Thanks in advance and let me know if you need any more info.
It's not enough to enable change tracking on the SQL side. You also need to set up an Integrated Change Tracking policy on your Azure Search datasource. This is described in the documentation
I'm looking at the features of SymmetricDS (last version symmetric-server-3.7.24) and in their forum I read it is actually possibile to synch from a view.
So I tried to synch from a view but when I run the program I got an error because symmetricDs cannot create a trigger on the view.
I also read that if a use a materialized view, then the trigger should be created.
The view is on a sqlserver 2008. I dropped the view and create a new one with schemabinding and add a cluster index on it. I also check that all the options are set as required in the MSDN guide to create indexed table.
I run symmetricDS again but still fail to create the trigger on the view.
Can anyone help me?
If what I ask is actually not possibile, then it is possibile to craete an extension that does not use trigger to synchronized the tables? I don't care that the two db are synched realtime, I can use a scheduled job, it will be just fine.
Thank you for you help and suggestion.
BTW: I can also change tool you you know a better one :)
I don't think that's a supported use case. However, you can try setting the sync_on_insert/update/delete fields to 0 on the sym_trigger. Then you would be able to sync the view with an initial load or by scheduling reloads (see "symadmin reload-table" command).