Yep - you should be able to use a rowversion (or timestamp) column in SQL Server to track changes and run a query like
SELECT * FROM YourTable
WHERE RowVersionCol > @LastKnownRowVersion;
The data type to use for @LastKnownRowVersion depends on whether the column is nullable or not. Since rowversion is an 8-byte binary value, for a non-nullable rowversion column, you can declare @LastKnownRowVersion as binary(8).
DECLARE @LastKnownRowVersion binary(8)
If the column were nullable (which is unusual, but possible), you would declare it as varbinary(8):
DECLARE @LastKnownRowVersion varbinary(8)
For a non-nullable rowversion column, you can safely use binary(8) for your parameter and compare it directly, because rowversion values always exist and are sequentially increasing within the database. If the column is nullable, you would have to handle the possibility of NULL values in your comparisons, but otherwise the same query works.
The key point is that rowversion is treated as a binary(8) value in SQL Server, so any variable or parameter used to compare against it must be compatible with binary(8) or varbinary(8) depending on nullability.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin