I can't join the I-hate-Oracle club as I've never managed to install the Developer Edition on a machine powerful enough that it runs. The last time, we installed on a 192MB RAM 600MHz box, that we often use for test runs with SQL Server 2000 (for small to medium scale systems). On this system, SQL Server 2000 takes 4 seconds to create a database (SQL Server creates a new database by making a copy of model). By contrast Oracle took all night (by which I mean 6+ hours) and still failed when the machine's DHCP lease ran out (the crappy Java client tool connected to the server on the same machine using TCP/IP).
So, I don't hate Oracle - but I'm not exactly motivated to find out.
Incidentally SQL Server 2005 runs quite happily in a 192MB Windows Server 2003 virtual machine on this 850MHz AMD Duron box (which has quite a lag on this editor!) I get the feeling SQL Server 2005 is going to blow Oracle out of the water.
Mike_Dimmick
@Mike_Dimmick
Best posts made by Mike_Dimmick
-
RE: Why the I-Hate-Oracle Club?
Latest posts made by Mike_Dimmick
-
RE: Microsoft tracert wtf
The ICMP packets containing the response contain the router's own idea of its IP address. If it's behind a NAT, it has no way of knowing what address will be seen the other side of the NAT.
-
RE: Trouble Finding a Date
@cm5400 said:
Geez, what the hell is this NTP thingy? I turned it off on all my rooters because it didn't look important. But, why won't my Windows stations syncronize with the time server? [:P] </SARCASM>
In case anyone didn't get that cm5400 was joking: there is a protocol for getting the time across a network. Unsurprisingly it's called Network Time Protocol [NTP]. The full NTP is really for synchronising among multiple computers to get sub-second accuracy - it's massive overkill for synchronising a workstation to a time source. There's a simplified version called Simple Network Time Protocol [SNTP] for this purpose - it simply clarifies the meaning of various fields in the protocol.
I recently implemented an SNTP client for Windows CE. It took less than 800 lines of C++ code, and that included correcting to the device's configured time zone and correcting for daylight savings time. This wouldn't have been necessary except for the fact that CE's automatic DST correction feature doesn't work reliably - sometimes it doesn't apply a DST offset when it should do.
Windows 2000 and later come with an SNTP client. On Win2k, it's not configured; on XP and 2003 it defaults to requesting the time from time.windows.com.
The Kerberos authentication protocol used in Active Directory domains requires that client machines have as small as possible time offset from the server - this allows the protocol to have short-lived validity on packets, preventing captured packets from being replayed. In a domain, by default, workstations and member servers get their time from the domain controller. The IT department should ensure that the DCs are synchronised with an external source.
In a standalone environment, you often find that your ISP provides an NTP server. To configure XP or 2003 to use a specific server, use the w32tm utility with the /config flag.
-
RE: Like a British sports-car
@memorex said:
Rollback segment exceeded: Nondeterministic sweeping of transactions... smart.
Me: It says we're out of rollback segment space- AGAIN!! The users are revolting, the Director is PISSED and is mailing every VP in the building.
DBA: You're kidding- we've got 10 segments and they're all set to X gigs...
Me: Wanna see the screen shot?... (looking at the segments) Each of them has 600 megs of dead transactions, why isn't it reusing any of them yet??
DBA: Dunno... guess I'll reboot it...
Me: (to myself) Brilliant solution...
Uh, were you performing full backups or transaction log backups? SQL Server 2000 won't discard old log entries if it thinks you're keeping backups of your database; the log space will only be reclaimed once the database or log is backed up. It starts out in minimally-logged mode but switches to maintaining complete logs once you've performed your first full backup. If you don't want to back up transaction logs, turn on SIMPLE logging.
Many other enterprise servers, e.g. Microsoft Exchange, maintain the required logs since the last full backup by default. If your data disk fails but the log disk is preserved, you can back up the log, then restore the last full backup to a replacement disk, then restore the log with recovery to roll forward to the point where the disk failure occurred.Mind you, rebooting should not cure the out-of-log-space problem!
-
RE: Why the I-Hate-Oracle Club?
I can't join the I-hate-Oracle club as I've never managed to install the Developer Edition on a machine powerful enough that it runs. The last time, we installed on a 192MB RAM 600MHz box, that we often use for test runs with SQL Server 2000 (for small to medium scale systems). On this system, SQL Server 2000 takes 4 seconds to create a database (SQL Server creates a new database by making a copy of model). By contrast Oracle took all night (by which I mean 6+ hours) and still failed when the machine's DHCP lease ran out (the crappy Java client tool connected to the server on the same machine using TCP/IP).
So, I don't hate Oracle - but I'm not exactly motivated to find out.
Incidentally SQL Server 2005 runs quite happily in a 192MB Windows Server 2003 virtual machine on this 850MHz AMD Duron box (which has quite a lag on this editor!) I get the feeling SQL Server 2005 is going to blow Oracle out of the water.