Project in a company that are heavy MSSQL Server users - is this a good/bad idea?

[YoJimbo]

Hello,

Though I know it is possible to use lift with MSSQL Server, I would
not imagine its not a popular approach. How good / bad an idea is it
to build a business critical app that forms the foundation of a large
company - on Lift connected to MSSQL Server 2008?

Previous experience we had years ago with the JDBC driver connected of
MSSQL Server was not great as there were bugs that due to the clash of
technologies were never fixed. Anyone have any recent experiences?

Many Thanks

[Andreas Joseph Krogh]

Building a Lift-based app with MS SQL Server is absolutely OK. I'm currently doing it and while MSSQL has its warts, so does any other DB. We're building a finance-app and have not encountered any bugs in neither the JDBC-driver nor MSSQL. We did switch from WLS to Tomcat+Atomikos due to some strange connection-pool bugs with XA which just disappeared when using Tomcat+Atomikos.

--

Andreas Joseph Krogh <and...@officenet.no>

Senior Software Developer / CTO

Public key: http://home.officenet.no/~andreak/public_key.asc

------------------------+---------------------------------------------+

OfficeNet AS            | The most difficult thing in the world is to |

Rosenholmveien 25       | know how to do a thing and to watch         |

1414 Trollåsen          | somebody else doing it wrong, without       |

NORWAY                  | comment.                                    |

Org.nr: NO 981 479 076  |                                             |

                        |                                             |

Tlf:    +47 24 15 38 90 |                                             |

Fax:    +47 24 15 38 91 |                                             |

Mobile: +47 909  56 963 |                                             |

------------------------+---------------------------------------------+

[Lance Walton]

Sadly, my current client uses prefers SQL Server, and uses it From a lot of Java apps (not through Lift though).

It doesn't seem to have problems that i could attribute due to JDBC drivers.

Regards,

Lance

> --
> You received this message because you are subscribed to the Google Groups "Lift" group.
> To post to this group, send email to lif...@googlegroups.com.
> To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
>

[David Pollak]

If I remember, Derek has done a lot of work on the MS SQL driver.  He's laying low for a few months (family expansion joy), but if any unexpected issues come up between Lift and MS SQL, we can get them fixed up quick for you.
 

Many Thanks

--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.

--
Lift, the simply functional web framework http://liftweb.net

Simply Lift http://simply.liftweb.net
Follow me: http://twitter.com/dpp
Blog: http://goodstuff.im

[Peter Petersson]

If you are in process of deciding on drivers you should check out the
JTDS driver.
Although Microsoft has its own jdbc driver the JTDS driver
http://jtds.sourceforge.net/ (a JDBC 3.0 driver) has proven to be really
good.
I have been using it in java enterprise production apps. for many years.
The Microsoft driver http://msdn.microsoft.com/en-us/data/aa937724.aspx
has probably also matured allot sins I last tested it ;-)
best regards
Peter Petersson

[Andreas Joseph Krogh]

On Fri, Jul 15, 2011 at 10:48 AM, Peter Petersson <peterss...@gmail.com> wrote:

If you are in process of deciding on drivers you should check out the JTDS driver.
Although Microsoft has its own jdbc driver the JTDS driver http://jtds.sourceforge.net/ (a JDBC 3.0 driver) has proven to be really good.
I have been using it in java enterprise production apps. for many years.
The Microsoft driver http://msdn.microsoft.com/en-us/data/aa937724.aspx has probably also matured allot sins I last tested it ;-)
best regards
  Peter Petersson

Actually, I would recommend against the JTDS-driver. I've had problems with it wrt. Stored Procedures. The com.microsoft.sqlserver.jdbc.SQLServerXADataSource works just fine for me.

Download it from http://www.microsoft.com/download/en/details.aspx?id=21599 

I've added it to our local nexus-repo so I can import it using Maven:

<dependency>

<groupId>com.microsoft.sqlserver</groupId>

<artifactId>sqlserver-jdbc4</artifactId>

<version>3</version>

</dependency>

[Sander Mak]

On Fri, Jul 15, 2011 at 11:39 AM, Andreas Joseph Krogh
<andrea...@gmail.com> wrote:
> On Fri, Jul 15, 2011 at 10:48 AM, Peter Petersson
> <peterss...@gmail.com> wrote:
> Actually, I would recommend against the JTDS-driver. I've had problems with
> it wrt. Stored Procedures.

I know it's a bit offtopic for this thread, but could you expand on
this? I'm currently using jTDS with stored procs quite a bit, and
would like to know what to watch out for.

Thanks,
Sander

[Andreas Joseph Krogh]

We're using both PostgreSQL and MSSQL with our app, and the jTDS-driver treated SPs in a non-standard way which made our Spring-based services fail executing SPs. So we ditched jTDS and used MS' instead and have had no problems ever since. I think it was due to some parameter-naming/parsing or so. I'm not aware of any data-loss scenarios or such using jTDS tho, so if you don't have any problems using it you might be OK.

[Andy Czerwonka]

Been using jTDS for years now and procs work just fine.

[Peter Petersson]

On 2011-07-15 19:17, Andy Czerwonka wrote:
> Been using jTDS for years now and procs work just fine. --
yea same here, It's a mature proven driver.

> You received this message because you are subscribed to the Google
> Groups "Lift" group.

> To view this discussion on the web visit
> https://groups.google.com/d/msg/liftweb/-/l7bfRXxNAQIJ.

[Andreas Joseph Krogh]

On 07/15/2011 08:02 PM, Peter Petersson wrote:
> On 2011-07-15 19:17, Andy Czerwonka wrote:
>> Been using jTDS for years now and procs work just fine. --
> yea same here, It's a mature proven driver.

Like I said; It might be stable, and mature etc., driver. But, it has
some none-standard issues which makes it a no-go if you care about
portable DB-access code. At least that's my experience.

--
Andreas Joseph Krogh <and...@officenet.no>
Senior Software Developer / CTO
Public key: http://home.officenet.no/~andreak/public_key.asc
------------------------+---------------------------------------------+
OfficeNet AS | The most difficult thing in the world is to |
Rosenholmveien 25 | know how to do a thing and to watch |

1414 Troll�sen | somebody else doing it wrong, without |

[Peter Petersson]

Interesting, can you give me some google pointers ?
I am not saying you are wrong I'm just curious on how JTDS is handling
"working with" store procedures in a non standard way.

I have to admit that after using JTDS for a couple of years I tried the,
at the time, new Microsoft driver (a ms revamped fork of jtds) because I
thought it would be a safer bet (at that time), the driver turned out to
lack in functionality (compared to JTDS) but I am sure it has matured a
lot since then and maybe it has even catch up with (or surpassed) JTDS
best regards
Peter Petersson

[Andreas Joseph Krogh]

On 07/15/2011 10:22 PM, Peter Petersson wrote:
> Interesting, can you give me some google pointers ?
> I am not saying you are wrong I'm just curious on how JTDS is handling
> "working with" store procedures in a non standard way.
>
> I have to admit that after using JTDS for a couple of years I tried
> the, at the time, new Microsoft driver (a ms revamped fork of jtds)
> because I thought it would be a safer bet (at that time), the driver
> turned out to lack in functionality (compared to JTDS) but I am sure
> it has matured a lot since then and maybe it has even catch up with
> (or surpassed) JTDS
> best regards
> Peter Petersson

It had to do with the way out-parameters were registered to SPs. With
jTDS we had this:

protected static final String BETANM = "@BETANM";
...
cStmt.registerOutParameter(BETANM, VARCHAR);

But that made the code incompatible with other DBs. When we switched to
MS' JDBC-driver we could write it the standard-way without the '@',
which made it work with PostgreSQL as well.

[Derek Chen-Becker]

The JTDS drivers are good and the SQL Server JDBC drivers themselves are vastly improved over the original releases (which were horrible abominations). One of my Lift apps at works integrates with SQL Server (2005, IIRC) and we haven't run into any issues with the MS drivers. If you do run into any issues with either JTDS or MS JDBC drivers please mail the list and we can take a look at it.

Derek