Change tracking version

I would like to get change tracking version for specific database(not the one stored procedure is running), something like:
SELECT someDB.dbo.CHANGE_TRACKING_CURRENT_VERSION();
Is that possible?
br, Simon

Have you enabled CDC in your database and for your table?
http://www.databasejournal.com/features/mssql/getting-starting-with-change-data-capture-cdc-in-sql-server-part-2.html
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Similar Messages

HT203128 iTunes 12.1.050 - Rollback: Updated from 12.01, now I cant't change track numbers and add additional data fields. How can I roll back to the previous version? @Apple, I want a $100 gift card for the inconvenience.

iTunes 12.1.050 - Rollback: Updated from 12.01, now I cant't change track numbers and add additional data fields. How can I roll back to the previous version? @Apple, I want a $100 gift card for the inconvenience.
- it's all said in the title. I can't understand why the developers turn things bad ... risking loosing Apples valuable customers.
More examples needed? (check out the communities and the reviews)
- OSX: Maverick to Yosemite = not recommended (check it out > http://roaringapps.com/apps)
- iPad: older versions as iPad2 should not upgrade to iOS7/8 (it's not supporting its hardware accordingly, it's designed for the latest hardware)
- iTunes (it's possible to rollback to 10.7 - 11.4, but you need to breech OSX system security framework)
- Pages (was a real alternative for many of us, each update reduced features and created incompatibility to older work files)
The list could easily extend to ...

You can offer Apple feedback here: http://www.apple.com/feedback/
as for "
"@Apple, I want a $100 gift card for the inconvenience"
dream on.

Change Tracking in SQL 2012 - Behavior Change

Hi,
We observed some change in behavior for Change Tracking feature in SQL 2012 Express. Sequence is as follows,
CT is not enabled at DB level. (Of course at table level too)
Created and populated table CTTEST with some rows, say 10 rows
Enabled CT at DB level
Enable CT for table CTTEST
Queried change tracking data, using change table function (select CT.* from CHANGETABLE(changes CTTEST, 0) CT). No rows returned. Perfect.
Updated few existing rows
Queried change tracking data using CHANGETABLE function as above. Now it returns the modified records. But SYS_CHANGE_OPERATION column shows as 'U', indicating update. Same scenario was tested in SQL 2008 Express, and we got SYS_CHANGE_OPERATION column
as 'I', indicating as Insert.
Is this a change in behavior? Can somebody clarify this?
Note: SQL Version is, "Microsoft SQL Server 2012 - 11.0.2100.60 (X64) Express Edition (Build 7601: Service Pack 1)"

Please note that I am not talking about CDC, but CT - Change Tracking and that too in Express edition.
Yes, I know, when we update primary key value, we will get a delete and insert transactions in CT. But my scenario is different. I am updating the rows, which are already available prior to enabling Change Tracking in that table. In that case only, I am
observing this.

Vendor changes tracking, Payment term filtering, Vendor listing

Hi All,
Need somebody help on the following points,
1- While changing the vendor via "process vendor and Bidder" (Business partner maintenance) transaction in EBP, the selection of payment term is restricted. That is in SPRO I can see lot of payment terms, but while changing the vendor some few payment terms are coming. Where is the filter? Can anybody guide me.
2- Vendor changes Tracking. In our project somebody has changed frequently the vendor indicators and details in EBP via process Vendor and Bidder(BP maintenance) transaction. But I couldnt able to track which fields are changed and by whom like in R/3. I tried in BP also, but only the address changed details are coming there. Can anybody guide me how to track the changes, if somebody changed somefield in EBP directly?
3- Vendor list - I want list ERS activated vendor in EBP. How to get the list of vendor for which ERS indicator is active? Please guide me.
Many thanks in Advance.
Regards
Shunmugaraj. T

Hi
Please refer to standard transaction - BBP_PD.. give any Shopping cart number, which is approved by a list of buyers, managers, etc..
Incase the changes are made, it will display all the details related to them in that case.
Understand its logic by putting break-point inside.
Incase you are using SRM 5.5 version, there is a report, which displays the changes made to the Purchase orders with old and new values.
Report name -> TERM_DISPLAY_CHANGE_HISTORY
Also please refer this as well.
Say you use this Function module for the change object - BUPA_BBP0060
This sample code will all the changes, if any, made to the object, with the old value and new values.
Here is the sample code for the FM ->
CHANGEDOCUMENTS_TO_OBJECT 
data: listtitle(80) type c.
data: objectclass like cdhdr-objectclas.
data: objecttitle(20) type c.
data: con_keylength(2) type n value 10.
data: cursor_field(20) type c.
listtitle = 'Changes made'.
listtitle+22 = vibebe-sberi.
listtitle+34 = vibebe-xberibz.
condense listtitle.
objectclass = 'BUPA_BBP0060'.
call function 'CHANGEDOCUMENTS_TO_OBJECT'
 exporting
 callmodus = callmodus
 cursor_field = cursor_field
 keylength = con_keylength
 listtitle = listtitle
 objectclass = objectclass
 objectid = objectid
 objecttitle = objecttitle
 exceptions
 error_in_function = 01
 invalid_field = 02
 others = 03.
if sy-subrc <> 0.
 message id sy-msgid type 'S' number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Change Tracker via Web Pane not working (when using multiple DF fields)

All,
We are using MDM 5.5 SP06, version 5.5.62.53
I have configured the Change Tracker so that I can use it in the Data Manager Web pane. I also set the configuration options of the Data Manager for the "Web Pane URL for selected records" to this link, so everything should work fine (it is working for another reporistory with just one DF field in the main table).
The main table (for which I want to track the changes on) has two DF fields. The first DF field of the main table is a look-up field (where the look-up table itself has two DF fields as well) and the second DF field of the main table is just a text field.
The URL link to the Change Tracker makes use of the parameter: searchrecord=<f:n>, as described in the reference guide for MDM Console.
When I select a record in the Record pane in the Data Manager and go to the Web Pane, then the Change Tracker is showing, but the change history for that record is not shown in the Change Tracker!!
This is caused by the fact that the records in the History table are stored with the following information in the "record" field (example): 113786=1000010 - Enfa B.V, 100075. Appearantly this is a combination of the two DF fields of the main table, and because the first DF field is a look-up it shows the values of the DF fields of the look-up table as well (including the ID of that look-up record)!!
I tried the following in the URL link: searchrecord=<f:n>,<f:n2>, but then the Change Tracker receives the following value (which is an invalid value): 1000010, Enfa B.V, 100075
How can I configure the URL link in the Console in such a way that the Change Tracker recognizes the searchrecord parameter as a valid entry (because when you start Change Tracker in separate browser it expects value of e.g. 113786=1000010 - Enfa B.V, 100075 in the "record" search field, otherwise it does not find any records).
Or do I need to change the DF fields and make an MDM-ID field to be the only DF field, and use that field in the searchrecord=<f:n> parameter???
Has anyone any experiences with this? Any suggestions how to solve this issue?
Thanks in advance,
Marcel

Hi,
We are indeed tracking changes on the main table. It is the standard SRM-MDM Catalog repository where Supplier and Supplier Part Number are the DF fields of the main table. From standpoint of the datamodel these two DF fields are correct, since these two fields make up an unique record.
Of course I can change the DF field and make the MDM-ID the DF field, but we want to stick as much as possible to the standard SRM-MDM Catalog!
It would be better if the URL to the Change Tracker has additional parameters that can be filled (like the Record Contains field instead of the Record field) or that you could specify the MDM-ID as parameter (without having to change the DF fields of the main table) so that the Change Tracker knows exactly for which record we require the change history!
I will investigate futher and see if we can live with the MDM-ID as the only DF field.
Thanks anyhow for your reply.
Regards,
Marcel

Enable Block Change Tracking in 11gr2

Hi Team,
If my database file system is in ASM..Can I enable blk change tracking in local filesystem?
Or IS it better to do in ASM? Any new features in 11gr2?
Regards,
Manohar

Do you plan running DUPLICATE against that DB?
If yes, you should place the Block Change Tracking File in a location that would enable you to effectively deal with this nasty bug:
"Bug 10193846 - RMAN duplicate fails with ORA-19755 when BCT file is not accessible [ID 10193846.8]"
Also, If you plan to use DUPLICATE, you should “name” your Block Change Tracking File, rather than going with the system name.
This advice applied only for 11gR2 versions that are affected by the bug.
Iordan Iotzov
http://iiotzov.wordpress.com/
Edited by: Iordan Iotzov on Oct 2, 2012 7:19 AM

OWB Change Management/Version Control Best Practice

Hi
I am about to start developing a data warehouse using OWB 10g R2, and I've been doing quite a lot of research into the various deployment/change management/version control techniques that can be used, but am still unsure which is the best to use.
We will have 2-3 developers working on the project, and will be deploying from Development, to Test, to Production (each will have a separate repository). We want to be able to easily identify changes made between 1 release and the next to have a greater degree of control and awareness of what goes into each release. We also wish to use a source control system to track changes (we'll probably use SVN, but I don't think that the actual SCS tool makes a big difference to our decision at this point).
The options available (that I'm aware of), are:
1. Full MDL export/import.
2. Snapshot MDL export/import.
3. Manual coding of everything using OMB Plus.
I am loath to use the full MDL export/import functionality since it will be difficult, if not impossible, to identify easily the changes made between 1 release and the next.
The snapshot MDL export/import functionality is a little better at comparing releases, but it's still difficult to see exactly what has changed between 1 version and the next - particularly when a change to a transformation has been made. It also doesn't cope that well with tracking individually made changes to different components of the model.
The manual coding using OMB Plus seems like the best option at the moment, though I keep thinking "What's the point of using a GUI tool, if I'm just going to code everything in scripts anyway?".
I know that you can create OMB Plus code generation scripts to create your 'creation' scripts, but the code generation of the Alteration scripts seems that it would be more complicated than just writing the Alteration scripts manually.
Any thoughts anyone out there has would be much appreciated.
Thanks
Liffey

Well, you can also do per-object MDL exports and then manage those in your version control system. With a proper directory structure it would be fairly simple to code an OMB+ Script that scans a release directory tree and imports the objects one by one. I have done this before, although if you are using OWB as the primary metadata location for database objects then you have to come up with some way to manage object dependency order issues.
The nice thing about this sort of system is that a patch can be easily shipped with only those objects that need to be updated.
And if you force developers to put object-level MDL into your version control system then your system should also have pretty reporting on what objects were changed for a release and why.
At my current job we do full exports of the project MDL and have a deployment script that drops the pre-existing deployed version of the project before importing and deploying the new version, which also works quite well - although as you note the tracking of what has changed in a release then needs to be carefully managed elsewhere. But we don't deploy any of our physical database objects through OWB. Those are deployed from Designer, and our patch script applies all physical changes first before we replace the mappings from the OWB project. We don't even bother synching the project metadata for tables / views / etc. at deployment. If the OWB project's metadata for database objects is not in sync with Designer, then we wind up with deployment errors. But on the whole it works pretty well.

Change Tracking many tables

Hi,
I have a number of tables that are all related in some way or another. Lets say there are 20 tables in total here. I need to track changes as they all ultimately will need their changes sending to some other remote database.
Is it ok for me to use just a single change version, obtained at the beginning of my synchronisation code, within a SNAPSHOT transaction for every table I'm concerned about?
I would also need to validate the change version used before getting changes for each table using CHANGE_TRACKING_MIN_VALID_VERSION wouldn't I?
Once I have obtained all the changes for the 20 tables, then I would commit my transaction.
Regards

The thing is, there is a LOT of overhead to tracking many tables. It is a seductive idea, but you may not realize the full cost in complexity and overhead.
Have you looked at using replication instead? It's not that much cheaper, but it may at least be easier.
I think you are confusing Change Tracking with Change Data Capture. SDA is talking about the former.
I am not sure that I fully understand SDA's question, but, yes, a single snapshot transaction sounds right. (For Josh: Change Tracking is best used with snapshot isolation.) Particularly, if you want to retrieve changes that are consistent with each
other.
I am a little worrried abotu "single change version", since the version number for each table will be different. (Or at least they can be.)
Erland Sommarskog, SQL Server MVP, [email protected]

RMAN block change tracking doubt

hi guys,
I want to speed up my RMAN incremental backup.So i decide to enable the block change tracking mechanism. How to implement it ? Should i create any file or set any parameters? plz guide me...
Oracle version:10.2.0.1.0
WindowsNT
TIA,

ALTER DATABASE
ENABLE BLOCK CHANGE TRACKING
USING FILE os_file_name;
use this command on the database level. As soon as the file kept the data change tracking, u will speed up ur increamental backups.

Block change tracking and Backup size

DB Version : 10gRelease
We have a Differential Incremental Backup strategy with Recovery Window retention policy. I haven't enabled BLOCK CHANGE TRACKING. Just would like to know if the backup size of both Level 0 and Level1 backups become smaller by enabling Block Change Tracking. Or is it just Level 1 backups' size which is going to decrease?
Thank you.

An excerpt from Oracle RMAN 11g Backup and Recovery by Robert G. Freeman & Matthew Hart
ISBN: 978-0-07-162861-7
The Block Change Tracking File
By default, when doing an incremental backup, any datafile that has changed in any way will be
backed up. This can make incremental backups take longer and will make them larger. RMAN
offers the ability to just back up changed database blocks. +This can make your incremental+
+database backups much smaller and shorter.+ To enable block change tracking, issue the command
alter database enable block change tracking. The result of this command will be the creation of a
file called the block change tracking file (BCTF).Checkout the word smaller.
Two things:
A. This is not Official oracle documentation ( Oracle press though)
B. This book is about 11g. I don't know if BCTF makes backups smaller in 11G.

Unable to deploy the .sca file for the Change tracker.

Hi all,
We can not able to deploy the change tracker through SDM as it is asking for the dependencies are missing.
Portal version EP 7.0 EHP1
MDM version 7.1 sp 5.
we have followed the below link for deploying
MDM change tracking with MDM 7.1 SP06 & EP version u2013 CE 7.2 SP01? but after downloading the MDM_WEB_UI from market place it is asking for 24+ dependencies for change tracker.
so please suggest.
regards,
Manohar.

Hello,
The version and the patch level should be same for MDM as well as EP.
Since this is an EP issue, for quick replies, post this in [Portal Forum|http://forums.sdn.sap.com/index.jspa?categoryID=1#2]
Regards,
Abhishek

Cannot trigger an update using simple relation and Change Tracking

I have a three entity master-detail setup. E3 has a domain key to E2 that has a domain key to E1. What I will like to see is a cascading attribute from the top (E1) being available (in the UI) for filtering in all three entities. In E1 no problem. In E2
no problem, using domain key relation and a BR for updating a secondary attribute from E1 to E2. Now, bringing the attribute further from E1 to E3 (via E2) is the issue.
1) if I make a BR in E3 that "equals" my shadow attribute in E3 to the E2.attribute, it populates the current value of the attribute, which is fine. But if the original attribute in E1 is updated the change is not reflected in E2/E3.
2) then I include the relevant attributes in E1, E2 in a change tracking group in order to catch the issue mentioned in 1). I have created a BR using "Has Changed" in CT group. But now the attributes is no longer updated at all. It is like the
first BR is being ignored. If I flag it as "Excluded", it works like in 1) again.
To me it seems like an attribute can only be updated using one "trigger", is that right? Any suggestions to how to populate a value based on the change of another attribute in the same entity as well as on an cascading update in the "parent"
entity?
This must a simple scenario for most people using multiple linked entities. Am I overcomplicating stuff here or is there a more simple approach? Any input is most appreciated.
On a side note, when is Change Tracking BR's executed? the records are flagged, but do I have to "apply BR" manually or use "validate version" for it to run? I would expect CT BT to execute in the background.
/Stig

>What I will like to see is a cascading attribute from the top (E1) being available (in the UI) for filtering in all three entities.
Why not just create a hierarchy and use that in the UI?
David
David http://blogs.msdn.com/b/dbrowne/

Not able to view actual Price updated 'Value' in Change Tracker

I was able to get my Change tracker to work and it is functioning. (SRM 5.0 MDM5.5 )... Configured Portal iViews for change tracker.
If I change a description I can see it in the change tracker application. But if I try and track a Price change it only shows me a date-time and user as to I when the price was changed it doesnu2019t show me the actual value changed, for my audit purposes.
On the portal the change tracker "Field" dropdown shows -> Price Updated. this is what is tracking any change of price.
In MDM Console-> Admin->Change Tracker I am tracking under Catalog Items: Price information, Price Updated, Special search terms, long description.
When I look at the Data manager in the Record Detail, I see u2018Price Updatedu2019 and it only has a Date and time stamp. In this same Record Detail, I see the field Price Information that contains :Lower bound, Purchasing Info record ID, Purchasing Organization, Amount and Currency. Amount-> contains the actual price value. This is what i want to see in the portal iView as Old value and New value....this is what I am unable to view? theres one small step i am not doing...
I am trying to track the actual change in the filed u2018Amountu2019u2026 I have tried to search for it in the Portal iView fields (table, record contains, fields, record)
cheers
alex

Hi Alex,
I would not here comment on change Tracking functionality but can you suggest another workaround to achieve this requirement. If it fits in your requirement you can go ahead with it.
In MDM, Create another field in Main table say Initial Price and for already existing field Amount replace its name with Updated Price in Qualified table Price.
now after this you will see that your by default Updated Price has values as it was your Amount field earlier and Initial Price field as empty. Now for next time, if any record comes using Import Manager then MDM workflow should trigger at Record Import.
This workflow contains following steps.
Start(Checkout)>Assign>Stop(CheckIn)
Assign step should have below expression and assignment:
Price Information.Updated Price
Where I am assuming Price Information is the field in main table which is look up to this qualified table Price.
So in this way you can maintain both existing and updated values of Price and cant then show in your Catalog.
suppose you have already existing record say 1 which has value of Amount as 20.
So that means you have Updated Price as 20 and Initial Price as empty(Null)
Now when same record 1 updates with new Amount say 40, it triggers this workflow on record import which will then assign value of existing updated Price 20 to Initial Field after that Updated Price will update by 40.
Note: This Assignment works well only if your main table record has this Qualified table link as single record. If your main table record contains more than one qualified links then this Assignment would not work fine. So use only if it fits.
Regards,
Mandeep Saini

Issue in change tracking table on subscriber after reinitialization the subscriber

Hi All,
We have enabled change tracking on the subscriber tables and its getting dropped during a reinitialization.we are running an ETL on the subscriber tables basing on change Tracking.Our Initial ETL runs once and incremental ETL runs after that but
after reinitialization i am getting fresh data and my initial ETL has already run.So how can i resolve this issue.Can't renireinitialization be done without disabling the Change Tracking.
Kindly provide your feedback.
Thanks

The article property Action if name is in use correlates to the
@pre_creation_cmd property of
sp_addmergearticle.
[ @pre_creation_cmd= ] 'pre_creation_cmd'
Specifies what the system is to do if the table exists at the subscriber when applying the snapshot.
pre_creation_cmd is nvarchar(10), and can be one of the following values.
Value
Description
none
If the table already exists at the Subscriber, no action is taken.
delete
Issues a delete based on the WHERE clause in the subset filter.
drop (default)
Drops the table before re-creating it. Required to support Microsoft SQL Server Compact Subscribers.
truncate
Truncates the destination table.
Brandon Williams (blog |
linkedin)

Issue in Change tracker application

Hi all,
We have enabled Change tracking in our repository when it was enabled there were only 3 Display fields in our repository and the tracking was done as is in the change tracking application under the column Record shows all the Display fields.
Now because of business requirements we have activated another field in our repository as a Display field, now when i login to change tracking application old records under Record column still shows the 3 Display fields in the Record column of the change tracker application.
I went and changed a record which falls in the Change tracking criteria, now i see 4 Display fields in the Record column of change tracker application as there are 4 display fields currently.
There is an in consistency in the data in the application now for few records there are 3 and 4 fields in the record column. Is this how the system behaves?
I think the logic is like this when ever there is a change happening in the repository, insert query is used to update the A2I_CM_History table with the existing data(at that moment how many fields were enabled as DISPLAY )with out any relationship to the Main table Display fields. Please correct me if i am wrong, it was just an assumption.
If any workarounds to this problem will be of a great help.
regards
Sowseel

Hi Gabor,
Thanks for your reply!
We have checked that note and we have indexes existing for few other fields as well in the table, but still we are facing the same issue.
Thanks & Regards,
Ravi

Change tracking version

Similar Messages

Maybe you are looking for