RE: MS SQL hasn't given up!

Yes and no. If your logs are backed up every 30 minutes, then you are effectively saying that you are willing to lose up to 30 minutes of transactions, in the event of failure on the TX logs (e.g. hardware). OTOH, Oracle can easily be made to be completely recoverable up to the last transaction ("no data lost") by duplicating, triplicating, etc. both the online redos and the archives.

Also, isn't the transaction log area in SQueaL Server in the DB itself and at a fixed size (as opposed to Oracle, where you can add redo groups on-the-fly)? In other words, if it fills up, what happens? Does it get overwritten or does the DB continue in an unrecoverable mode?

Trying to understand more of this wonderful Enterprise product...

Rich

Rich Jesse                        System/Database Administrator
rich.jesse_at_qtiworld.com           Quad/Tech International, Sussex, WI USA

-----Original Message-----
Sent: Friday, February 28, 2003 11:05 AM To: Multiple recipients of list ORACLE-L

Sorry but point 7 isn't exactly true.

Transaction logging does take place and can be backed up for reapplication to a database backup.

Its not perhaps as well implemented as Oracle's but I have a system with the

transaction log backed up every 30 minutes.

The implementation is different but the effect is the same with the ability to do point in time recovery. And they do have log shipping capability in SQL Server 2000 (Enterprise).

The point that really bothered me was the lack of multiplexing the writes to

the transaction logs (redo). DB2/UDB has it. The MSS method (only option) is to Mirror.

David

>From: Jan Pruner <jan_at_pruner.cz>
>Reply-To: ORACLE-L_at_fatcity.com
>To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com>
>Subject: Re: MS SQL hasn't given up!
>Date: Fri, 28 Feb 2003 07:19:10 -0800
>
>Fresh in memory because 2 days ago I had meeting with MS SQL people from
>Microsoft.
>I will talk about MS SQL 2000 Enterprise.
>1. MS SQL cannot handle exception. There is nothing like EXCEPTION WHEN ...
>THEN.
>
>2. MS SQL has nothing like package.
>
>3. MS SQL has nothing like partitioned table (next release in 2 years will
>have)
>
>4. There is nothing like INSERT NOLOGGING. You have start/stop logging for
>whole session.
>
>5. There's nothing like sequence (Well, IDENTITY column IS NOT sequence).
>
>6. Well, you can use undocumented function pwdencrypt and pwdcompare to
>store
>passwords (the same hash function for storing users password is using MS
>SQL)
>:-)
>
>7. There is nothing like ARCHIVE MODE in MS SQL.
>

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Jesse, Rich
  INET: Rich.Jesse_at_qtiworld.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).