PHWinfo banniere

Titres
PORTAIL ANNUAIRE ARTICLES COMPARATEUR HÉBERGEURS DEVIS FORUMS RÉDUCTEUR D'URL
Précédent   PHWinfo > Autres forums > Forum Programmation & Conception > comp.databases.mysql > Where to start?
S'inscrire FAQ Membres Recherche Messages du jour Marquer les forums comme lus
Where to start?

Réponse
 
LinkBack Outils de la discussion
Vieux 15/10/2007, 19h33   #1
Chuck
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Where to start?

I'm an oracle dba that has been tasked with learning mysql in case our
dept. is ever asked to start supporting it. Where is the best place to
start?

We will probably be running it on Solaris 8 or Solaris 10.

Is there much difference between enterprise and community versions other
than support? I don't want to buy enterprise version until I actually
get a project that requires it.

TIA.
  Réponse avec citation
Vieux 15/10/2007, 20h25   #2
Good Man
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Where to start?

Chuck <skilover_nospam@bluebottle.com> wrote in news:ivNQi.719$H92.369
@trnddc07:

> I'm an oracle dba that has been tasked with learning mysql in case our
> dept. is ever asked to start supporting it. Where is the best place to
> start?
>
> We will probably be running it on Solaris 8 or Solaris 10.
>
> Is there much difference between enterprise and community versions other
> than support? I don't want to buy enterprise version until I actually
> get a project that requires it.


No need at all to buy the enterprise version. Go for the community one...
  Réponse avec citation
Vieux 15/10/2007, 20h46   #3
Chuck
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Where to start?

Good Man wrote:
> Chuck <skilover_nospam@bluebottle.com> wrote in news:ivNQi.719$H92.369
> @trnddc07:
>
>> I'm an oracle dba that has been tasked with learning mysql in case our
>> dept. is ever asked to start supporting it. Where is the best place to
>> start?
>>
>> We will probably be running it on Solaris 8 or Solaris 10.
>>
>> Is there much difference between enterprise and community versions other
>> than support? I don't want to buy enterprise version until I actually
>> get a project that requires it.

>
> No need at all to buy the enterprise version. Go for the community one...


What should I start with terms of reading materials for documentation
and to learn this critter?

I will probably be running the db server on Solaris 10. Most of the
clients will be Windows. I'll probably be administering it from a Linux
workstation. Which GUI tools should I use?

TIA
  Réponse avec citation
Vieux 15/10/2007, 21h06   #4
Good Man
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Where to start?

Chuck <skilover_nospam@bluebottle.com> wrote in
news:aAOQi.720$H92.134@trnddc07:

> Good Man wrote:
>> Chuck <skilover_nospam@bluebottle.com> wrote in
>> news:ivNQi.719$H92.369 @trnddc07:
>>
>>> I'm an oracle dba that has been tasked with learning mysql in case
>>> our dept. is ever asked to start supporting it. Where is the best
>>> place to start?
>>>
>>> We will probably be running it on Solaris 8 or Solaris 10.
>>>
>>> Is there much difference between enterprise and community versions
>>> other than support? I don't want to buy enterprise version until I
>>> actually get a project that requires it.

>>
>> No need at all to buy the enterprise version. Go for the community
>> one...

>
> What should I start with terms of reading materials for documentation
> and to learn this critter?
>
> I will probably be running the db server on Solaris 10. Most of the
> clients will be Windows. I'll probably be administering it from a
> Linux workstation. Which GUI tools should I use?


The client machines OS doesn't really matter at all. In terms of
documentation, you'll find the manual pretty darn ful in itself.
Otherwise, I'd say pick a publisher and head to Amazon for a book.

GUI tools, it all depends. Some people don't use any at all. Personally,
I'm a big fan of Navicat: http://www.navicat.com/

Good luck!
  Réponse avec citation
Vieux 15/10/2007, 21h15   #5
Chuck
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Where to start?

Good Man wrote:
>
> GUI tools, it all depends. Some people don't use any at all. Personally,
> I'm a big fan of Navicat: http://www.navicat.com/
>
> Good luck!


I think thinking about the GUI tools on the mysql.com web site. Will I
need any of them?
  Réponse avec citation
Vieux 15/10/2007, 21h21   #6
Good Man
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Where to start?

Chuck <skilover_nospam@bluebottle.com> wrote in
news:v%OQi.724$H92.472@trnddc07:

> Good Man wrote:
>>
>> GUI tools, it all depends. Some people don't use any at all.
>> Personally, I'm a big fan of Navicat: http://www.navicat.com/
>>
>> Good luck!

>
> I think thinking about the GUI tools on the mysql.com web site. Will I
> need any of them?


They're ful, but you don't *need* any of them. MySQL Administrator is
a good one, and many people like the Query Browser.
  Réponse avec citation
Vieux 15/10/2007, 21h35   #7
Chuck
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Where to start?

Good Man wrote:
>
> GUI tools, it all depends. Some people don't use any at all. Personally,
> I'm a big fan of Navicat: http://www.navicat.com/
>
> Good luck!


I was thinking about the GUI tools on the mysql.com web site. Will I
need any of them?
  Réponse avec citation
Vieux 15/10/2007, 23h04   #8
Kees Nuyt
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Where to start?

On Mon, 15 Oct 2007 19:35:42 GMT, Chuck
<skilover_nospam@bluebottle.com> wrote:

>Good Man wrote:
>>
>> GUI tools, it all depends. Some people don't use any at all. Personally,
>> I'm a big fan of Navicat: http://www.navicat.com/
>>
>> Good luck!

>
>I was thinking about the GUI tools on the mysql.com web site.
>Will I need any of them?


Not really.
My favourite 'GUI tools' are a simple ASCII editor and a
generic shell script for testing.
I always start with a 'schema file' which begins with
"DROP DATABASE ...;" and testdata for every table.

While developing, I seldomly edit tables in the database,
because it is generally faster to edit my schema source
and load everything all over again. For a testdatabase
loading the schema and test data typically only takes a
few seconds.
Clicking in a GUI is usually slower.
I only use PHPMyAdmin to browse tables and to test queries
before adding them to the schema as views.
--
( Kees
)
c[_] Giving power and money to government is like giving
whiskey and car-keys to teenage boys. (PJ O'Rourke) (#291)
  Réponse avec citation
Vieux 01/11/2007, 21h11   #9
Mike
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Where to start?


"Chuck" <skilover_nospam@bluebottle.com> wrote in message
news:iiPQi.726$H92.635@trnddc07...
> Good Man wrote:
>>
>> GUI tools, it all depends. Some people don't use any at all.
>> Personally,
>> I'm a big fan of Navicat: http://www.navicat.com/
>>
>> Good luck!

>
> I was thinking about the GUI tools on the mysql.com web site. Will I
> need any of them?



You may find some of them useful. Worth a look at, depends what you are
intending to do.
You might want to have a look at sqlyog which is pretty good
HTH









---------------------------------------------------
DSB
http://www.documentscanningbureau.com



  Réponse avec citation
Réponse


Outils de la discussion

Règles de messages
Vous ne pouvez pas créer de nouvelles discussions
Vous ne pouvez pas envoyer des réponses
Vous ne pouvez pas envoyer des pièces jointes
Vous ne pouvez pas modifier vos messages

Les balises BB sont activées : oui
Les smileys sont activés : oui
La balise [IMG] est activée : oui
Le code HTML peut être employé : non
Trackbacks are oui
Pingbacks are oui
Refbacks are oui


Fuseau horaire GMT +1. Il est actuellement 09h24.


Édité par : vBulletin® version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0 RC5 Tous droits réservés.
Version française #16 par l'association vBulletin francophone
PHWinfo est un site Éducation Sans Frontières ©2000-2008
Ad Management by RedTyger
©Tous droits réservés par les parties respectives
Page generated in 0,15642 seconds with 17 queries