Nokia SQL Manager

[Tesla]

Anyone know of any worthwhile sql managers for mobiles?
Particularly MS 2000/5/8

I have a nokia 5800

 

[ToxicBunny]

SQL manager for a phone??!!??!?! wth would you need something as daft as that?

 

[Tesla]

Here's a crazy notion. Say I'm having lunch with family or friends over a weekend. A distressed client phones. Now I could walk all the way to my car to fetch my laptop or just try to troubleshoot from my mobile first. I just think it could make a 24x7 support environment easier.

 

[guest2013-1]

Here's a crazy notion. Say I'm having lunch with family or friends over a weekend. A distressed client phones. Now I could walk all the way to my car to fetch my laptop or just try to troubleshoot from my mobile first. I just think it could make a 24x7 support environment easier.

Have a look at web based sql managers. I'm sure some of them now have support for mobile phones (screen size et all)

What I'm concerned about though is:

1) Client working over a weekend on a faulty database?
2) The database being faulty in the first place?
3) ... see 1 and 2?

I've had 0 calls over a weekend because of database issues...

 

[ToxicBunny]

I'd also be horribly worried about exposing a DB to the world so you could use a mobile manager rather than spending 2 mins to go and fetch your laptop and remote into work and use a decently secured connection.

 

[Tesla]

Why must people always shoot something down?

Have a look at web based sql managers. I'm sure some of them now have support for mobile phones (screen size et all)

What I'm concerned about though is:

1) Client working over a weekend on a faulty database?
2) The database being faulty in the first place?
3) ... see 1 and 2?

I've had 0 calls over a weekend because of database issues...

I've not looked into the web based side of things. That could also be a viable option.

1) No, I'm referring to the client who uses applications connected to a vast array of dbs. A lot of businesses run over weekends. The estimate of 50-100 dbs per dba is laughable and really not [my] reality.
2) Not necessarily faulty, it could be anything administrative or trouble-shooting related. Anyway, and by that logic why not just fire all dba's around the world seeing as these things run themselves right?

Surely one weekend does not constitute the base for a support response initiative.

I'd also be horribly worried about exposing a DB to the world so you could use a mobile manager rather than spending 2 mins to go and fetch your laptop and remote into work and use a decently secured connection.

Firstly surely a secure connection is dependent on the software and protocol methodology implemented. I really don't think always having your laptop with you is really practical.

I know I'm going a bit on the offensive here, but jeesh, I thought I would get some constructive feedback here, not the attitude I'm receiving.

Yes I know, boo-hoo.

 

[ToxicBunny]

I'm just trying to figure out the logic behind it tbh.... I know you say the 24x7 support thing.... which is vaguely justifiable in my books, but not really enough given just how crippled a SQL manager on a phone will be.

Then again, it also depends entirely on what you're going to be doing with it I suppose.... I couldn't cope with a Sql Manager on a phone screen, hell I need a large WS for SQL because of what I do with it...

As for the number of dbs per DBA.... 50-100 is on the low side in my experience....

 

[Other Pineapple Smurf]

Well I convinced the company to get a netbook to handle our support calls as since I started using mine for support its perfect. I've used our Nokia E75 to ssh into our servers (no security issue) but its not all that practical.

Its not your idea thats being knocked its more the practical application of it.

I've tried to do SQL queries on various smartphones while ssh'd into our servers and its so time consuming without a proper sized keyboard.

 

[guest2013-1]

Why must people always shoot something down?

I've not looked into the web based side of things. That could also be a viable option.

1) No, I'm referring to the client who uses applications connected to a vast array of dbs. A lot of businesses run over weekends. The estimate of 50-100 dbs per dba is laughable and really not [my] reality.
2) Not necessarily faulty, it could be anything administrative or trouble-shooting related. Anyway, and by that logic why not just fire all dba's around the world seeing as these things run themselves right?

Surely one weekend does not constitute the base for a support response initiative.

LOL, well.. you see.. I'm lazy.. and lazy people usually do things right the first time around so there won't be any maintenance.

99.95% of the time when I do have a fault "in the db" (aka data problem "breaking" stuff) it's because of the software. And 100% of the time it's not my software. So i have to isolate the incident, figure out why it's err'ing and then fix the data.

I've done that a total of 2 times this year.

So grabbing my laptop out of my car quick and doing it wasn't much of a hassle. for safety reasons I usually have my laptop with me and inside the house at all times anyway

People break into cars you know