On Thu, 21 Sep 2006 11:36:11 +0100, Adrian B wrote:
> "Adrian B" <adrianmarsbradshaw@yahoo.com> wrote in message
> news:45126a97.0@entanet...
>>
>> with my user "adrian" I can't create a schema
>> I can't login as root
>>
>> So here's the problem. When I run the Migration Tool, I can only login
>> with my user "adrian", but it fails to create the new schema and I hit a
>> brick wall.
>
> Update : I just created the schema as root on the server PC and the
> Migration Tool seems to be doing its stuff...
>
> Is that the best way of doing things?

Depends on how secure your setup is. If all this is on a private network
and not exposed to the outside, it's probably not unreasonable to allow
the root ID to be logged in from the WinXP box. Take a look at the GRANT
commands in the manual, with special focus on the 'user'@'host' bits.

Personally, I allow root to log in from elsewhere, have my own user ID
given authority to *most* things, and give each automatic process its
own "functional id" with a VERY limited access profile; pretty much just
what the ID is expected to be able to do. (Mostly, this is just SELECT,
INSERT, and UPDATE. Sometimes DELETE. Almost no functional IDs have
DROP or CREATE, for example, and none have GRANT. GRANT is something
that I reserve for root.)

--
I think it's a beautiful day to go to the zoo and feed the ducks.
To the lions.
-- Brian Kantor