Online Data Transform: applications

Showing posts with label applications. Show all posts

Friday, March 9, 2012

OODBMS vs RDBMS

What applications/cases benefit from OODBMS as opposed to RDBMS.
We are considering OODBMS to replace some SQL Server instances but dont
really know if we are making the right choice.
Can someone just provides pros and cons of both ?
ThanksOn 21 Apr, 03:01, "Hassan" <has...@.hotmail.com> wrote:
> What applications/cases benefit from OODBMS as opposed to RDBMS.
> We are considering OODBMS to replace some SQL Server instances but dont
> really know if we are making the right choice.
> Can someone just provides pros and cons of both ?
> Thanks
As far as I'm aware there is no reliable and standard definition of
what constitutes an OODBMS. You might get more help if you tell us the
product name.
Why are you considering a change if you don't know what the benefits
are?
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--|||ObjectStore and Versant
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
news:1177162193.874920.238980@.y80g2000hsf.googlegroups.com...
> On 21 Apr, 03:01, "Hassan" <has...@.hotmail.com> wrote:
>> What applications/cases benefit from OODBMS as opposed to RDBMS.
>> We are considering OODBMS to replace some SQL Server instances but dont
>> really know if we are making the right choice.
>> Can someone just provides pros and cons of both ?
>> Thanks
> As far as I'm aware there is no reliable and standard definition of
> what constitutes an OODBMS. You might get more help if you tell us the
> product name.
> Why are you considering a change if you don't know what the benefits
> are?
> --
> David Portas, SQL Server MVP
> Whenever possible please post enough code to reproduce your problem.
> Including CREATE TABLE and INSERT statements usually helps.
> State what version of SQL Server you are using and specify the content
> of any error messages.
> SQL Server Books Online:
> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
> --
>|||Comparisons of only loosely related technologies without reference to the
requirements are pointless. You will need to say what you're trying to do
from an application point of view.
Each of the options - SQL Server, ObjectStore (I don't know Versant) has its
strengths and weaknesses, so it all depends on what you're trying to do.
"Hassan" <hassan@.hotmail.com> wrote in message
news:OYb2zdChHHA.4140@.TK2MSFTNGP05.phx.gbl...
> ObjectStore and Versant
> "David Portas" <REMOVE_BEFORE_REPLYING_dportas@.acm.org> wrote in message
> news:1177162193.874920.238980@.y80g2000hsf.googlegroups.com...
>> On 21 Apr, 03:01, "Hassan" <has...@.hotmail.com> wrote:
>> What applications/cases benefit from OODBMS as opposed to RDBMS.
>> We are considering OODBMS to replace some SQL Server instances but dont
>> really know if we are making the right choice.
>> Can someone just provides pros and cons of both ?
>> Thanks
>> As far as I'm aware there is no reliable and standard definition of
>> what constitutes an OODBMS. You might get more help if you tell us the
>> product name.
>> Why are you considering a change if you don't know what the benefits
>> are?
>> --
>> David Portas, SQL Server MVP
>> Whenever possible please post enough code to reproduce your problem.
>> Including CREATE TABLE and INSERT statements usually helps.
>> State what version of SQL Server you are using and specify the content
>> of any error messages.
>> SQL Server Books Online:
>> http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
>> --
>

OODBMS vs RDBMS

Saturday, February 25, 2012

Only enable the string truncation prevention of ANSI_WARNINGS

I'm working with some long standing VB/SQL Server applications and for
the second time we've suffered from having the parameters to a stored
procedure call get silently truncated now that the data field has got
much larger than when the code was developed all those years ago. This
is always very hard to debug and I'd really like SQL Server to throw
an error when this happens.

I don't feel confident enablying the full ANSI_WARNINGS as it is
likely to affect lots of functionality in the database in
unanticipated ways.

What I'd like to be able to do is enable only the ANSI check for the
string data getting truncated but haven't been able to find a way to
do this. Is it possible?

Cheers
Dave"David Sharp" <dave@.daveandcaz.freeserve.co.uk> wrote in message
news:ca434844.0401080924.40dd7da1@.posting.google.c om...
> I'm working with some long standing VB/SQL Server applications and for
> the second time we've suffered from having the parameters to a stored
> procedure call get silently truncated now that the data field has got
> much larger than when the code was developed all those years ago. This
> is always very hard to debug and I'd really like SQL Server to throw
> an error when this happens.
> I don't feel confident enablying the full ANSI_WARNINGS as it is
> likely to affect lots of functionality in the database in
> unanticipated ways.
> What I'd like to be able to do is enable only the ANSI check for the
> string data getting truncated but haven't been able to find a way to
> do this. Is it possible?
> Cheers
> Dave

There's no 'subset' of ANSI_WARNINGS which will only raise an error on
string truncation, so your best bet is to fix your application, either by
making the stored proc parameter longer, or by validating the input in the
front end.

If neither of those are possible, then there aren't many options left,
except perhaps to raise an error if the parameter value is the same size as
the maximum possible size of the parameter data type. So if you have
char(20), assume that only values up to 19 characters are valid. But it
would be much better to fix the problem at the source, and validate the
input.

Simon|||David Sharp (dave@.daveandcaz.freeserve.co.uk) writes:
> I'm working with some long standing VB/SQL Server applications and for
> the second time we've suffered from having the parameters to a stored
> procedure call get silently truncated now that the data field has got
> much larger than when the code was developed all those years ago. This
> is always very hard to debug and I'd really like SQL Server to throw
> an error when this happens.
> I don't feel confident enablying the full ANSI_WARNINGS as it is
> likely to affect lots of functionality in the database in
> unanticipated ways.
> What I'd like to be able to do is enable only the ANSI check for the
> string data getting truncated but haven't been able to find a way to
> do this. Is it possible?

To add to what Simon said, you would probably have any use for ANSI_WARNINGS
anyway. ANSI_WARNINGS produces an error if you try to assign a column
a value which is too long. However, variable and parameter assignment
still truncates silently, even with ANSI_WARNINGS ON.

I would however encourage you to switch to ANSI_WARNINGS for other reasons.
This setting is required is some contexts, more precisely in distributed
queries and when you used indexed views and indexed computed columns.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland Sommarskog <sommar@.algonet.se> wrote in message news:<Xns946B48FD1863Yazorman@.127.0.0.1>...
> I would however encourage you to switch to ANSI_WARNINGS for other reasons.
> This setting is required is some contexts, more precisely in distributed
> queries and when you used indexed views and indexed computed columns.

Thanks for your help. Sounds like there's no short cut to identify
when this happens. We'll have to physically go through and make sure
it is checked for in each sproc.

Cheers
Dave

Friday, March 9, 2012

OODBMS vs RDBMS

OODBMS vs RDBMS

OODBMS vs RDBMS

Saturday, February 25, 2012

Only enable the string truncation prevention of ANSI_WARNINGS

Online Data Transform

Blog Archive

About Me