Jared,
I was going to respond, but you did a great job for me. Your points were my points
exactly. I really tried to go to the SQL*Server class with an open mind thinking "I'm
adding a skill set", but I found myself constantly comparing to Oracle. I didn't mean
to start the Holy War again,
I find both the observations Jim made during the class and the remarks from the
SqlServer list as both interesting. Having worked with SQL*Server as well as
being an Oracle addict I observe that we each view our RDBMS choices as the best
there is which is kind of valid. It's just very interestin
See below...
>
> Backups directly to tape require the tape to be attached
> locally to SQL Server.
> >> Okay, if you really want to transfer your 10+GB
> database over the
> >> network each night, I suppose you will need to use Oracle.
>
> JS: 10+GB over the network is trivial. If yo
> Rich
>
>
>> From: [EMAIL PROTECTED]
>> Reply-To: [EMAIL PROTECTED]
>> To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
>> Subject: Fw: Just got back from SQL*Server 2000 training...
>> Date: Tue, 19 Feb 2002 08:08:21 -0800
>>
>>
We run a couple of production systems in noarchivelog. This is due to
how they operate. They are reporting datamarts and the nightly loads
would generate way to much redo to contain. Since all the data
originates elsewhere recovery just means redoing a load. Any OLTP
should be in archivel
Couldn't resist responding to this.
*Cannot take DB out of "archivelog" mode. Can limit what is posted to txn
log, but cannot stop it.
>> Why would you want to? So you have the remote possibility
>> of ending up with a corrupt, unrecoverable database if the
>> power supply on the sy
CLE-L <[EMAIL PROTECTED]>
>Subject: Fw: Just got back from SQL*Server 2000 training...
>Date: Tue, 19 Feb 2002 08:08:21 -0800
>
>I sent this e-mail to a friend who works with SqlServer and he sent this to
>a SqlServer list as You can see from headers
>
>Here are comments of
Archivelog mode -
I don't like putting test databases in archivelog mode. Or databases that are updated
once a day. Redo logs are adequate to recover from a power system failure.
Mirroring -
The problem with relying on hardware mirroring is that it mirrors everything -
corruption, delete comm
> - Original Message -
> To: "SQL 7 Discussions" <[EMAIL PROTECTED]>
> Sent: Tuesday, February 19, 2002 5:29 PM
>
> *When txn log fills up, have to just "truncate" the log in order for
> processing to continue. Leaves system vulnerable until you get a full DB
> backup.
> >> Seems a l
I sent this e-mail to a friend who works with SqlServer and he sent this to
a SqlServer list as You can see from headers
Here are comments of a member :-
Gints Plivna
IT Sistçmas, Meríeïa 13, LV1050 Rîga
http://www.itsystems.lv/gints/
- Original Message -
To: "SQL 7 Discussion
Maybe because I heard that Sybase finally implemented row-level locking. As
of v10 (and I thought at least early 11 releases), the base unit of locking
was the block. And that was the end of my 6-month stint programming with
Sybase. Then there was that Interbase fiasco I had before being found
[Jeremiah Wilton]
> How about the good old "readers can block writers?" That one never
> fails to make jaws drop. Not just SQL Server, though. Informix and
> Sybase too.
Is there a specific list of DBMS systems (Oracle is definitely one,
obviously) where "readers don't block writers and writer
geez, that (and the truncate log problem) were there back when I worked
with Sybase 4.7
they STILL haven't fixed those problems? WHY does anyone use this?
--- Jeremiah Wilton <[EMAIL PROTECTED]> wrote:
> How about the good old "readers can block writers?" That one never
> fails to make jaws dr
Jeremiah,
Do you have an example / link to details of this.
Is it just long running "verbs" - eg a full table scan, that can block writers or is
there more to this in the case of SQL Server?
Thanks,
Bruce Reardon
-Original Message-
Sent: Tuesday, 19 February 2002 8:18
To: Multiple reci
How about the good old "readers can block writers?" That one never
fails to make jaws drop. Not just SQL Server, though. Informix and
Sybase too.
--
Jeremiah Wilton
http://www.speakeasy.net/~jwilton
On Mon, 18 Feb 2002, Jim Hawkins wrote:
> During the class, I kept a list of all the "I can't
During the class, I kept a list of all the "I can't believe this is really the case
with SQL*Server..." items, and thought you might all like to see it. These are just
notes I took on a Palm Pilot, so forgive me if they are a litte undetailed. I walked
away from the class thinking, "this is j
16 matches
Mail list logo
