| Summary: | Add database support for Microsoft SQL Server 2008 | ||
|---|---|---|---|
| Product: | [Technology] Jubula | Reporter: | Markus Tiede <markus.tiede> |
| Component: | Core | Assignee: | Markus Tiede <markus.tiede> |
| Status: | CLOSED WONTFIX | QA Contact: | Oliver Goetz <Oliver.Goetz> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | alexandra.schladebeck |
| Version: | 1.2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Markus Tiede
We recently evaluated adding support for "Microsoft SQL Server 2008" databases and decided not to do so due to the following reasons: - The default database transaction isolation level for "Microsoft SQL Server 2008" is "READ COMMITTED". This leads to blocked reads during database write operations e.g. when importing Jubula projects into the database or saving test cases - which causes the client to "hang" permanently during these operations. This issue might be resolved by adjusting the database isolation level but it would require manual adjustment of the database setup and / or default behavior. - "Microsoft SQL Server 2008" uses a different behavior for evaluating uniqueness of <code>null</code> values (http://connect.microsoft.com/SQLServer/feedback/details/299229/) than is specified in the standard, which causes some of our unique constraints to fail despite being correct. based on the results of the evaluation, I am closing this ticket. |