Jump to content


Photo
- - - - -

ProIV & SQL Server 2005


8 replies to this topic

#1 Sean Graves

Sean Graves

    Member

  • Members
  • PipPip
  • 13 posts
  • Gender:Male
  • Location:United Kingdom

Posted 12 July 2006 - 09:12 AM

Has anybody used SQL Server 2005 with ProIV Version 5.5 on Windows 2003 Server / Windows XP Professional ?

If so have you had any differculties using with ProIV or have you found it worked with no problems ?

#2 Ian Blew

Ian Blew

    Member

  • Members
  • PipPip
  • 15 posts
  • Gender:Male
  • Location:United Kingdom

Posted 12 July 2006 - 02:36 PM

We have tried our application running PROIV 5.5 against a SQL 2K5 database on a Windows 2003 Server.

I'm not sure if it's our application architecture, but we have had problems with locking and deadlocks. It appears that SQL 2K5 has a new locking algorithm - a search for "SQL Server 2005 locking" on Google may provide some insights.

Please note that PROIV do not support SQL Server 2005 until PROIV v6.

#3 Rob_Stebbens

Rob_Stebbens

    Member

  • Members
  • PipPip
  • 30 posts
  • Gender:Male

Posted 12 July 2006 - 02:54 PM

Sean,
have you tried dropping the compatibility level back down to SQL Server 2000? (will be called 8.0 by the Database ) also check your Isolation level....


Say hi to everyone at PDS <_<

Rob.

#4 mdexter

mdexter

    Advanced

  • Members
  • PipPipPip
  • 70 posts
  • Gender:Male

Posted 13 July 2006 - 12:00 AM

We did some very preliminary testing with our application and didn't find any problems. However, we didn't do enough testing to uncover any muti-user locking / deadlock type of issues. In terms of installation and just running the application through a quick test, we didn't find any problems. Mark Dexter

#5 Sean Graves

Sean Graves

    Member

  • Members
  • PipPip
  • 13 posts
  • Gender:Male
  • Location:United Kingdom

Posted 14 July 2006 - 11:05 AM

Thanks for all the above replies.

I have only done a quick simple test as a one user against SQL 2005 Express.
I did not get any issues but as you all now the moment you include more than one user things start to happen.

So always useful to know if anyone has been there first :)

Thanks again

#6 Mike Schoen

Mike Schoen

    Expert

  • Members
  • PipPipPipPip
  • 198 posts
  • Gender:Male
  • Location:Guelph, Canada

Posted 18 October 2007 - 12:59 PM

We have just done some testing with the latest 5.5 release and sql 2005 express, and have found the following deadlock issue.

This is done using a pro-iv non-paging screen, with one file in change mode, and no full-function sql - ie a plain pro-iv function.

Session 1 reads a record in change mode
Session 2 tries to read the same record, and gets a record lock, waiting for file
Session 1 accepts the changes by entering through the screen, and gets a deadlock rollback.
Session 2 then gets the record, and can carry on and save it's changes.

Very strange, if we get a resolution to this, I will post it here.

#7 Marlon

Marlon

    Member

  • Members
  • PipPip
  • 29 posts
  • Gender:Male

Posted 19 June 2008 - 03:31 PM

Hello,
Does anybody have any more news on using v5.5 with SQL Server 2005? Basically, I need to know if it works or doesn't work.

Cheers,
Marlon

This is your captain speaking. We may experience some slight turbulance and then...explode.


#8 Neil Hunter

Neil Hunter

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 414 posts
  • Gender:Male
  • Location:Johannesburg, South Africa

Posted 20 June 2008 - 07:20 AM

Express or Enterprise?

Had 5.5r543 running on a client site on Express
Our one dev server runs 55r543 with SQL2005 Enterprise

So yes it does work and in theory you shouldn't have any issues as long as you use the correct ODBC driver....

Reading Mike's post above, we did get around this by setting an environment variable. Can't remember what it was off hand...

Edited by Neil Hunter, 20 June 2008 - 07:22 AM.


#9 Neil Hunter

Neil Hunter

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 414 posts
  • Gender:Male
  • Location:Johannesburg, South Africa

Posted 20 June 2008 - 07:27 AM

LOCKED_ROWS_RETURNED=YES
SQL_TRANSACTION_ERROR=YES

were set in our ini file. It would also seem that 6.1 behaves in a similar way if the variables are not set. Anybody else found this?



Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users