There is requirement that I want rows affected by delete operation in sybase any one if know please do let me know.
There is not sufficient documentation for sybase as I see.
According to : https://archive.sap.com/discussions/thread/3732742 did you checked this?
master.monProcessStatement.RowsAffected
Related
I want complete rca for table deleted or drop in snowflake, not sure how the table got deleted. any hints how I can see who have deleted it ? as all the dependent pipes got failed.
You might be able to use the Access_History view.
Details: https://docs.snowflake.com/en/user-guide/access-history.html#write-operations-in-the-access-history-view
Also, on more of when and who did it - query-history-view
Details: https://docs.snowflake.com/en/sql-reference/account-usage/query_history.html#query-history-view
I'm really new to apache-nifi, I'm not sure this can be achieved in the nifi processor or not?
Say I have a table called "USArrests":
Before update
The first record of "Murder" is 15.5.
After update
The first record of "Murder" changed to 13.2.
How can this change be detected by setting the processor if possible?
Solved with the following:
Remove binlog_do_db from my.cnf.
Not able to explain why. Will update answer when I know (if someone does, please explain).
I have a query regarding the merge replication. Is there any stored procedure which gives me exactly the column values that have been changed at the server, because of which the row will be replicated to the subscriber in the next replication session ?
I have looked at this link http://www.replicationanswers.com/Script9.asp which allows me to get the info of all the rows that need to be replicated. But i want to know the specific columns that have changed for these rows.
You can reference sys.sp_showlineage and possibly sys.sp_showcolv, but you are heading down a path of system internals which requires a great deal of learning and understanding.
Anyone know why sql server prevents inserting from within the WHEN MATCHED clause of a MERGE statement? I understand that the documentation only allows updates or deletes, I'm wondering why this is the case so I can understand merge better.
Look at this post for an example.
If you are trying to merge your source to your target, it does not make sense to insert a line if it was found in the target. You may want to update or delete it though. Inserting what is already there would create duplicates.
As you want to INSERT when you find a MATCH, i presume the condition of the ON-clause is met but another field is different. Consider including this field into the ON-clause with AND to differentiate between present rows and to be inserted rows.
Common sense says: if you already have it there (the record) why would you want to insert it again? Not to mention that normally the "matching" is on a non duplicated key.
If you are able to find a situation where a matched record needs to be inserted again, let us know to help you.
I think the case might be if I want to keep track of history. e.g. Telephone field; I want to see what was the telephone before you change it.
I am working on Sybase. Want to implement pagination for a result. I can get first few records by stating set rowcount 100 But is there any way to set start point as well. The result is ordered on basis of a text value.
I tried finding at stackoverflow as well as in Sybase documentations, but could not find the way. I tried Limit, rownum() etc. but they are not supported. Also tried putting it as inner query, but somehow it is not working.
One solution I found which was of creating temp table with identity and get the same. But to the application, I do not have create table permission.
Can someone please help me in this?
You should use START AT. Try:
SELECT TOP 25 START AT 50 * FROM TABLE1 ORDER BY Id
LIMIT and OFFSET are supported in ASE 16, see https://help.sap.com/viewer/cbed2190ee2d4486b0bbe0e75bf4b636/16.0.3.7/en-US/c1881eb182ee4b899f54c577d9dc0ecb.html