On Thu, 24 Feb 2005 16:54:37 -0500, Dave Watts [EMAIL PROTECTED] wrote:
Of course you can trust MS-SQL -- it's a great database. I'd
ask what kind of idiot leaves port 1433 open on a MS-SQL
server in the first place (due to the number of infections
with the various worms, apparently a
Don't be security arrogant.
-Adam
On Tue, 1 Mar 2005 09:04:27 -0500, John Paul Ashenfelter
[EMAIL PROTECTED] wrote:
On Thu, 24 Feb 2005 16:54:37 -0500, Dave Watts [EMAIL PROTECTED] wrote:
Of course you can trust MS-SQL -- it's a great database. I'd
ask what kind of idiot leaves port 1433
On Tue, 1 Mar 2005 09:30:41 -0500, Adrocknaphobia
[EMAIL PROTECTED] wrote:
Don't be security arrogant.
-Adam
Actually, it should be Don't be security *ignorant*.
--
John Paul Ashenfelter
CTO/Transitionpoint
(blog) http://www.ashenfelter.com
(email) [EMAIL PROTECTED]
As an aside, there are *plenty* of ways to scan for open SQL
Sever ports on your network to find those MSDE installs, so
I'll maintain that anyone with an unsecured SQL Server of any
type is, in fact, and idiot.
That's all well and good, but many people using products which include MSDE
Agreed, that original statement reeks of idiocy itself.
-Original Message-
From: Dave Watts [mailto:[EMAIL PROTECTED]
Sent: 01 March 2005 16:17
To: CF-Talk
Subject: RE: Securing MS-SQL port 1433 [WAS Re: Pro/Con Moving from MSSQL to
MySQL]
As an aside, there are *plenty* of ways
On Thursday 24 Feb 2005 17:05 pm, toru okada wrote:
sorry jochem, i am going to have to resepectfully disagree with you
I willing to bet if I give MSSQL a huge wodge of data, and then pull the power
plug out while it's doing something, it'll take a while to recover too.
Hell, even Oracle
I know that we will have to rewrite anything that we have
Don't you still lose the ability to use views, stored procedures,
triggers and custom functions with the latest versions of MySQL?
4.0.x, using InnoDB tables gives you transaction support.
4.1 supports subqueries
5.0 (alpha) supports
Mark W. Breneman wrote:
We are in the early stages of *thinking* about moving away from MS SQL
server and moving to MySQL.
Why? What do you hope to gain from this move?
Jochem
~|
Find out how CFTicket can increase your
I can give you two good reasons. LiveJournal and Wikipedia. In the
past couple of months both of these websites went down due to power
issues in their coloco facilities. It took a bit of effort to bring
both of these sites back up because the database was in an
inconsistent state. Both sites
On Thu, 24 Feb 2005 10:04:22 -0600, Mark W. Breneman
[EMAIL PROTECTED] wrote:
We are in the early stages of *thinking* about moving away from MS SQL
server and moving to MySQL. Can anyone give me a quick pro / con points for
doing this or not doing this?
I'm a big MySQL fan, and a long-time
Message-
From: Jochem van Dieten [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 24, 2005 10:07 AM
To: CF-Talk
Subject: Re: Pro/Con Moving from MSSQL to MySQL
Mark W. Breneman wrote:
We are in the early stages of *thinking* about moving away from MS SQL
server and moving to MySQL.
Why
Ashenfelter [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 24, 2005 11:19 AM
To: CF-Talk
Subject: Re: Pro/Con Moving from MSSQL to MySQL
On Thu, 24 Feb 2005 10:04:22 -0600, Mark W. Breneman
[EMAIL PROTECTED] wrote:
We are in the early stages of *thinking* about moving away from MS SQL
server
Well, whatever you think of Microsoft, SQL Server is far far better then
mySQL will ever be (cost aside that is!).
-Original Message-
From: Mark W. Breneman [mailto:[EMAIL PROTECTED]
Sent: 24 February 2005 16:27
To: CF-Talk
Subject: RE: Pro/Con Moving from MSSQL to MySQL
Yeah, I
NOW()? Surely you mean GETDATE()?
-Original Message-
From: Adkins, Randy [mailto:[EMAIL PROTECTED]
Sent: 24 February 2005 16:26
To: CF-Talk
Subject: RE: Pro/Con Moving from MSSQL to MySQL
Another point to consider is in MySQL you can not use
A default date field to be auto-populated
Mark W. Breneman wrote:
We are configing a new windows 2000 webserver server and the owner walked up
and just asked out of the blue what if we install MySql and not MSSQL. (and
no this was not a Dilbert Pointy haired Boss sorta moment.) We have talked
about moving to a non Windows platform
: Mark W. Breneman [mailto:[EMAIL PROTECTED]
Sent: 24 February 2005 16:27
To: CF-Talk
Subject: RE: Pro/Con Moving from MSSQL to MySQL
Yeah, I thought that question might come up...
We are configing a new windows 2000 webserver server and the owner walked up
and just asked out of the blue
To: CF-Talk
Subject: RE: Pro/Con Moving from MSSQL to MySQL
Another point to consider is in MySQL you can not use A default date field
to be auto-populated as you can in MS-SQL using the NOW() function.
I had to modify my code to accommodate that function.
But for the most part I rather enjoy MySQL
Subject: RE: Pro/Con Moving from MSSQL to MySQL
NOW()? Surely you mean GETDATE()?
-Original Message-
From: Adkins, Randy [mailto:[EMAIL PROTECTED]
Sent: 24 February 2005 16:26
To: CF-Talk
Subject: RE: Pro/Con Moving from MSSQL to MySQL
Another point to consider is in MySQL you can
On Thu, 24 Feb 2005 10:15:34 -0600, toru okada [EMAIL PROTECTED] wrote:
I can give you two good reasons. LiveJournal and Wikipedia. In the
past couple of months both of these websites went down due to power
issues in their coloco facilities. It took a bit of effort to bring
both of these
that is!).
-Original Message-
From: Mark W. Breneman [mailto:[EMAIL PROTECTED]
Sent: 24 February 2005 16:27
To: CF-Talk
Subject: RE: Pro/Con Moving from MSSQL to MySQL
Yeah, I thought that question might come up...
We are configing a new windows 2000 webserver server and the owner walked
up
One is the obvious question of, have you thought of PostgreSQL? It is
much more feature rich than MySQL and is now also a native Windows app
with version 8 (previously it wasn't, at least as standard).
--
Damien McKenna - Web Developer - [EMAIL PROTECTED]
The Limu Company -
toru okada wrote:
I can give you two good reasons. LiveJournal and Wikipedia.
They are not reasons to stay away from MySQL, just examples of
misconfigured systems and bad behaving OS'es.
What might be a reason is that the default configuration of MySQL
offers no data integrity protection in
On Thu, 24 Feb 2005 08:33:40 -0800, Spike [EMAIL PROTECTED] wrote:
That's a ridiculous thing to say without at least qualifying it.
Agreed. No better than blithely saying MySQL rules because it's open source :)
MySQL is a far better tool for me than MSSQL because as a developer I
often need
, 2005 11:25 AM
To: CF-Talk
Subject: RE: Pro/Con Moving from MSSQL to MySQL
NOW()? Surely you mean GETDATE()?
-Original Message-
From: Adkins, Randy [mailto:[EMAIL PROTECTED]
Sent: 24 February 2005 16:26
To: CF-Talk
Subject: RE: Pro/Con Moving from MSSQL to MySQL
Another point
Actually, that's not fair at all. You can use T-SQL and the osql
command line just as effectively, though it takes more steps and isn't
as intuitive since MS has forced you to think GUI. It takes a
similar amount of steps to restore a database through the MySQL
Administrator GUI too if
Another point to consider is in MySQL you can not use
A default date field to be auto-populated as you can in
MS-SQL using the NOW() function.
GETDATE() -- NOW() Is Access... or does MySQL use now() also?
s. isaac dealey 954.927.5117
new epoch : isn't it time for a change?
add features
Mark W. Breneman wrote:
We are configing a new windows 2000 webserver server and
the owner walked up
and just asked out of the blue what if we install MySql
and not MSSQL. (and
no this was not a Dilbert Pointy haired Boss sorta
moment.) We have talked
about moving to a non Windows
Damien McKenna wrote:
One is the obvious question of, have you thought of PostgreSQL? It is
much more feature rich than MySQL and is now also a native Windows app
with version 8 (previously it wasn't, at least as standard).
Hey, you stole my line!
There are a number of other alternatives to
I know that we will have to rewrite anything that we have
used MSSQL
functions and MSSQL SQL commands.
Less than you think needs rewritten -- MySQL has lots of
common MS-SQL
(and Oracle, etc) commands built-in or aliased to the
native MySQL
functions. The only difference in very common
On Thu, 24 Feb 2005 17:45:01 +0100, Jochem van Dieten
[EMAIL PROTECTED] wrote:
They are not reasons to stay away from MySQL, just examples of
misconfigured systems and bad behaving OS'es.
sorry jochem, i am going to have to resepectfully disagree with you
here. This would not happen with a
The example I gave was just that, an example. There are
plenty more such
as the ability to dump a database table to an SQL script.
That can be
handy if you need to send some sample data to another
developer.
There's a 3rd party GUI tool called SqlYob (I think) for MySQL that
handles a lot
On Thu, 24 Feb 2005 11:43:28 -0500, John Paul Ashenfelter
[EMAIL PROTECTED] wrote:
Wow, what a load of FUD. Neither LiveJournal nor Wikipedia blame the
outages on MySQL.
Nor did I say that. What I said is that because of the power failure
their databases where left in a inconsistement
On Thu, 24 Feb 2005 11:39:41 -0500, Adkins, Randy
[EMAIL PROTECTED] wrote:
Well whichever, MySQL does not have that functionality.
I wish it did. But still, I do enjoy using MySQL rather
than MS-SQL. But that is my personal choice
Actually, MySQL has an entire field type for handling
Adkins, Randy wrote:
Another point to consider is in MySQL you can not use
A default date field to be auto-populated as you can in
MS-SQL using the NOW() function.
I had to modify my code to accommodate that function.
But for the most part I rather enjoy MySQL.
But OTOH, there's the
toru okada wrote:
On Thu, 24 Feb 2005 17:45:01 +0100, Jochem van Dieten
[EMAIL PROTECTED] wrote:
They are not reasons to stay away from MySQL, just examples of
misconfigured systems and bad behaving OS'es.
sorry jochem, i am going to have to resepectfully disagree with you
here. This
I think you mean SQLYog,
I've used it quite a bit in the past and it's very handy if you aren't a
command line junkie, or can't remember the specific syntax of a command.
Spike
S. Isaac Dealey wrote:
The example I gave was just that, an example. There are
plenty more such
as the ability to
toru okada wrote:
On Thu, 24 Feb 2005 17:45:01 +0100, Jochem van Dieten wrote:
They are not reasons to stay away from MySQL, just examples of
misconfigured systems and bad behaving OS'es.
sorry jochem, i am going to have to resepectfully disagree with you
here. This would not happen
One is the obvious question of, have you thought of
PostgreSQL? It is
much more feature rich than MySQL and is now also a native
Windows app
with version 8 (previously it wasn't, at least as
standard).
--
Damien McKenna - Web Developer -
[EMAIL PROTECTED]
The Limu Company -
Jochem van Dieten wrote:
Damien McKenna wrote:
One is the obvious question of, have you thought of PostgreSQL? It is
much more feature rich than MySQL and is now also a native Windows app
with version 8 (previously it wasn't, at least as standard).
Hey, you stole my line!
There are a
Keith Gaughan wrote:
Adkins, Randy wrote:
Another point to consider is in MySQL you can not use
A default date field to be auto-populated as you can in
MS-SQL using the NOW() function.
I had to modify my code to accommodate that function.
But for the most part I rather enjoy MySQL.
I used the windows version of PostgreSQL on a pretty big project last
year. The deployment was on *nix, but I was developing on Windows.
The only gotcha I ran into was that the pid file sometimes got left
behind if PostgreSQL terminated unexpectedly. That resulted in me not
being able to start
Jochem van Dieten wrote:
free Open Source arena there is Firebird, Ingress, Derby and
derby? well lets see what hani has to say about it:
http://www.jroller.com/page/fate/
~|
Logware (www.logware.us): a new and convenient
ah. Sterile and dispassionate. This guy needs to learn how to express himself.
:D
--
--mattRobertson--
Janitor, MSB Web Systems
mysecretbase.com
~|
Logware (www.logware.us): a new and convenient web-based time tracking
Paul Hastings wrote:
Jochem van Dieten wrote:
free Open Source arena there is Firebird, Ingress, Derby and
derby? well lets see what hani has to say about it:
http://www.jroller.com/page/fate/
The line about it being 01:30 probably explains most :-)
But for some serious research into
Of course you can trust MS-SQL -- it's a great database. I'd
ask what kind of idiot leaves port 1433 open on a MS-SQL
server in the first place (due to the number of infections
with the various worms, apparently a lot)?
This doesn't really have anything to do with the thread, but to answer
Yep, that would be the one.
I think you mean SQLYog,
I've used it quite a bit in the past and it's very handy
if you aren't a
command line junkie, or can't remember the specific syntax
of a command.
Spike
s. isaac dealey 954.927.5117
new epoch : isn't it time for a change?
add
Jochem van Dieten wrote:
The line about it being 01:30 probably explains most :-)
ah you know i love ibm (where would i be without icu4j) but that stuff
about their registration process the docs is so on the mark. don't
know if it's because of the docs but their OSS staff are more than
47 matches
Mail list logo
