ScrollableCursor not working on Microsoft SQL Server 2005?

Question

Hi all,
I'm using a scrollable cursor to get read only data from some very large database tables. I'm using the following code:
private Scrollable cursor;
private ScrollableCursor getCursor() {
    if (cursor == null) {
        ReadAllQuery query = JpaHelper.getReadAllQuery(getJpaQuery());
        query.setLockMode(ReadAllQuery.NO_LOCK);
        query.setIsReadOnly(true);
        query.useScrollableCursor(getPageSize());
        query.dontAcquireLocks();
        query.setFetchSize(getPageSize());
        Server server = getServerSession();
        Session session = server.acquireClientSession();
        cursor =  (ScrollableCursor)session.executeQuery(query);
    return cursor;
public Collection<T> findAll(int firstResult, int maxResults) {
    setPageSize(maxResults);
    ArrayList<T> result = new ArrayList<T>();
    getCursor().absolute(firstResult);
    for(int i = 0; i < maxResults; i++){
        if(getCursor().hasNext()){
            result.add((T)getCursor().next());
        }else{
            break;
    return result;
}This approach works fine on the DB2 server at my client's headquarters. The same code has to be used on a MS SQL server as well. However, I get the following error:
Exception [EclipseLink-4002] (Eclipse Persistence Services - 1.0 (Build SNAPSHOT - 20080207)): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: com.microsoft.sqlserver.jdbc.SQLServerException: The cursor type/concurrency combination is not supported.
Error Code: 0
Call: SELECT ..... FROM ... WHERE ...ORDER BY ... ASC
     bind => [....]
Query: ReadAllQuery(com.mycompany.package.Class)
I googled the SQLServer error description, and found this forum thread. Apparently, EclipseLink is requesting a insensitive, updatable ResultSet from SQL Server. I don't understand it, since I did call query.setIsReadOnly(true). Is there a way to influence the type of cursor that EclipseLink will use? According to the mentioned forum thread, I should be fine if EclipseLink uses a sensitive, updatable cursor.
Any help would be highly appreciated!
Best regards,
Bart Kummel

Answer 1

Never mind, I figured it out myself. Perhaps I was a little bit too fast with posting a question this time. For those who want to know: I had to change:
    query.useScrollableCursor(getPageSize());to
    ScrollableCursorPolicy policy = new ScrollableCursorPolicy();
    policy.setPageSize(getPageSize());
    policy.setResultSetConcurrency(ScrollableCursorPolicy.CONCUR_READ_ONLY);
    query.useScrollableCursor(policy);This code is better in all cases, because the previous version probably created unnecessary locks, even if the database supported it. I still do not understand why I have to set both the Query and the ScrollableCursor to read only, though.
Best regards,
Bart Kummel