[dba-Tech] More command language options than ever

Most of the POS apps I install at various client sites are setup,
calibrated, remotely connected, last updates installed, network configured
and users setup all through a very sophisticated set of batch file scripts.

Only if some process fails or locks up do I get a chance to cleanup and
reset the scripts. The last install must of comprised of 5000 plus lines of
script in 30 different files.

Jim  

-----Original Message-----
From: dba-tech-bounces at databaseadvisors.com
[mailto:dba-tech-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Thursday, May 07, 2009 2:20 PM
To: Discussion of Hardware and Software issues
Subject: Re: [dba-Tech] More command language options than ever

Good reference.

Yep, there are still a lot of things that at least easier and in many cases
only possible  with a 
CLI command.

Just a couple of days ago, I  put a "Shell("IPCONFIG /FLUSHDNS") in a
mailing application 
loop to solve a problem with SMPT errors caused by WIndows DNS caching.

 

On 7 May 2009 at 10:46, Jim Lawrence wrote:

> There seems to be more command language options than ever. Check out the
> following list from MS:
> http://technet.microsoft.com/en-us/library/cc772390(WS.10).aspx. 
> 
> I bet you there are a number even the most learnered of us have never seen
> let alone used. It appears that the predictions of the death of the
command
> line to the graphic interface has been greatly exaggerated.
> 
> Jim
> 
> _______________________________________________
> dba-Tech mailing list
> dba-Tech at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-tech
> Website: http://www.databaseadvisors.com


_______________________________________________
dba-Tech mailing list
dba-Tech at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/dba-tech
Website: http://www.databaseadvisors.com