SQL Server 2000 and mySQL4.1.*
-
Can I install mySQL4.1.* along with my SQL Server 2000 and
-
and what??
Did you try?
Are you having problems doing that?
I don't see why they couldn't work together (assuming it's a testing/dev environement... an sql server should be use just for that).
-
haven't tried it yet, I was hoping I could get more inputs should others have tried it before
-
At school I had :
ms sql server
mysql
vb6
vb net
office
php
msdn
+15 more I forget
never had a problem
-
Great! tnx for sharing
-
I prefer to go down the virtual PC route myself, keeps everything seperated and lets me break things during testing without having to rebuild the PC from scratch.
-
HTH.
-
In a production environment, unless you have really good hardware and loads of memory, I would always suggest a dedicated server for any Client Server RDMS, as all are designed to use all available resources and can conflict.
If you are talking about a development server or workstation, then be aware of the need for partitioning the resources for each to be happy, they don't share.
Plus if you have problems each vendor will point at the other and you will be all on your own.
Reminds me of a Joke: Don't attempt to install Wife 2.0 while still connected to Wife 1.0, they are not compatible...
Andy
-
and try not to install 'mistress.exe' as that results in all sorts of problems.
How about this one
Breakfast.com halted: Cereal port not responding
-
Damn we're geeks
. -
-
Software Compatablity Alert-
Last year, I upgraded my Girlfriend 5.0 to Girlfriend 5.1, which
installs itself as "Fiancee 1.0". Recently, I upgraded Fiancee 1.0 to
Wife 1.0 and it's a real memory hog. It has taken up all my space,
and Wife 1.0 must be running before I can do ANYTHING.
It is also spawning Child Processes which are further consuming
system resources. Some applications, such as PokerNight 10.3,
BeerBash 2.5, and PubNight 7.0 are no longer able to run in the
system at all.
Additional plug-ins were automatically installed, such as
Mother-In-Law 55.8, and there is no uninstall feature for these
plug-ins. No mention of these behaviors was discussed in the
brochures or documentation, although other users have reported
similar problems.
Because of this, some users that I know have decided to avoid the
headaches associated with these upgrades, and simply move from
Girlfriend 5.0 to Girlfriend 6.0. Unfortunately, this is not without
peril as well, as all traces of Girlfriend 5.0 must be removed from
the system before attempting installation of 6.0.
Even then, Girlfriend 6.O will repeatedly run system checks (usually
in the background, and often late at night when the system is asleep)
to find evidence of previous versions. To cap it off, Girlfriend 6.0
apparently has a nag feature reminding me about the advantages of
upgrading to wife 1.0.
However, I do like some of the features that you are planning to
include In the upcoming Girlfriend 6.1. release:
* A "Don"t remind me again" button
* Minimize button
* Shutdown feature
* An install shield feature so that Girlfriend can be completely
uninstalled if necessary (so you don't lose cache and other objects)
Unfortunately, since I've already upgraded to Wife 1.0, I don't think
I will be able to take advantage of any of these new features, unless
you decide to include them in the next Mistress release. But, of
course, there is a whole raft of problems associated with the use of
Mistress 1.0 and Wife 1.0 on the same system -- most notably are
system conflicts and continual disk thrashing, which starts shortly
after Wife 1.0 detects Mistress 1.0.
Interestingly enough, all versions of PersonalLawyer still work fine.
Finally, Wife 1.0 apparently deletes all MSMoney files before
uninstalling itself; following that, Mistress 1.1 will refuse to
install, claiming insufficient resources. I personally find all these
new tools and conflicts to be too confusing and time consuming. I'm
sticking with Dog 1.0b3. It slobbers and chews up the paper, but all
in all these bugs are tolerable. It is simple to operate and we get
along fine.
-
Sounds like a rootkit to me
-
The mistake most people make is that they think wife 1.0 and wife 2.0 are utilities, but in fact it's a complete OS that controls all of your resources.
You only get it to run smoothly when you often run YESDEAR.EXE and FLOWERS.EXE. Sometimes when you make mistakes (like trying to install mistress 1.0) your only option is to run the very expensive JEWELRY.EXE.
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply