[sllug-members]: RE: sllug-members Digest, Vol 44, Issue 3

Robert Frazier robert.frazier at achieveglobal.com
Wed Apr 2 12:39:50 MST 2008


Use Oracle :-) It behaves very nicely on Linux...


-----Original Message-----
From: sllug-members-bounces at sllug.org
[mailto:sllug-members-bounces at sllug.org] On Behalf Of
sllug-members-request at sllug.org
Sent: Wednesday, April 02, 2008 1:00 PM
To: sllug-members at sllug.org
Subject: sllug-members Digest, Vol 44, Issue 3

Send sllug-members mailing list submissions to
	sllug-members at sllug.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://www.sllug.org/cgi-bin/mailman/listinfo/sllug-members
or, via email, send a message with subject or body 'help' to
	sllug-members-request at sllug.org

You can reach the person managing the list at
	sllug-members-owner at sllug.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of sllug-members digest..."


Today's Topics:

   1. Re: Microsoft SQL Server (John M. Anderson)
   2. Re: Microsoft SQL Server (Doran L. Barton)
   3. Re: Microsoft SQL Server (Kevin Pendleton)
   4. Re: Microsoft SQL Server (Jackman)
   5. Re: Microsoft SQL Server (Corey Edwards)
   6. Re: Grub Error (Kyle Waters)


----------------------------------------------------------------------

Message: 1
Date: Tue, 1 Apr 2008 09:11:42 -0600
From: "John M. Anderson" <sontek at gmail.com>
Subject: Re: [sllug-members]: Microsoft SQL Server
To: Salt Lake Linux Users Group Discussions <sllug-members at sllug.org>
Message-ID: <20080401151123.GD11215 at cerebrum.lan>
Content-Type: text/plain; charset=us-ascii

On Tue, Apr 01, 2008 at 05:45:55PM -0600, Jackman wrote:
> Ladies and Gentlemen,
> 
> Where I work, everything revolves around a row of very large servers
> with MS Windows NT running Microsoft SQL Server.  To connect to this
> server, I use primarily Microsoft SQL Query Analyzer and Microsoft
> Enterprise Manager.  My work is generally very tedious, mostly because
> MS software doesn't script very well.  I can bring my laptop into
> work, however, or install cygwin and work from those machines if I so
> desired.  Scripting and collecting data would be so much easier on a
> linux box.  Still, I know that MySQL is the SQL database preference on
> Linux systems and so I am having a difficult time finding anything
> that advertises itself being compatible with Microsoft SQL Server.
> Does it even matter?  Thank you for your help and I look forward to
> your input.

You can use UnixODBC with FreeTDS or Monodevelop... Monodevelop has a 
nice gui, but if you are looking for scripting support I'd just use
UnixODBC. Any tool that supports ODBC should be able to connect to
MSSQL.


------------------------------

Message: 2
Date: Tue, 1 Apr 2008 20:20:23 -0600
From: "Doran L. Barton" <fozz at xmission.com>
Subject: Re: [sllug-members]: Microsoft SQL Server
To: Salt Lake Linux Users Group Discussions <sllug-members at sllug.org>
Message-ID: <20080402022023.GA10999 at xmission.com>
Content-Type: text/plain; charset="us-ascii"

Not long ago, Jackman proclaimed...
> Where I work, everything revolves around a row of very large servers
> with MS Windows NT running Microsoft SQL Server.  To connect to this
> server, I use primarily Microsoft SQL Query Analyzer and Microsoft
> Enterprise Manager.  My work is generally very tedious, mostly because
> MS software doesn't script very well.  I can bring my laptop into
> work, however, or install cygwin and work from those machines if I so
> desired.  Scripting and collecting data would be so much easier on a
> linux box.  Still, I know that MySQL is the SQL database preference on
> Linux systems and so I am having a difficult time finding anything
> that advertises itself being compatible with Microsoft SQL Server.
> Does it even matter?  Thank you for your help and I look forward to
> your input.

It should be fairly straight forward to connect to a M$-SQL server from
Perl (using the DBI module) or Java (using JDBC and/or Hibernate). The
UnixODBC folks < http://www.unixodbc.org/ > can probably provide some
more
information about command-line utilities for more generic interaction,
but
if you're looking for the ability to automate/script queries and other
database operations, I would highly recommend Perl+DBI.

-- 
Doran L. Barton <fozz at xmission.com> - Linux, Perl, Web, good fun, and
more!
 "Auto Repair Service. Free Pick-up and delivery.  Try us once, you'll
  never go anywhere again."
    -- Classified ad in newspaper
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://sllug.org/pipermail/sllug-members/attachments/20080401/f3bd19b4/a
ttachment-0001.pgp

------------------------------

Message: 3
Date: Tue, 01 Apr 2008 21:32:04 -0600
From: Kevin Pendleton <kevin at roundsphere.com>
Subject: Re: [sllug-members]: Microsoft SQL Server
To: sllug-members at sllug.org
Message-ID: <47F2FE34.3050604 at roundsphere.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

sllug-members-request at sllug.org wrote:
> From: Jackman <kd7nyq at gmail.com>
> Subject: [sllug-members]: Microsoft SQL Server
> To: "Salt Lake Linux Users Group Discussions"
> 	<sllug-members at sllug.org>
>
> Ladies and Gentlemen,
>
> Where I work, everything revolves around a row of very large servers
> with MS Windows NT running Microsoft SQL Server.  To connect to this
> server, I use primarily Microsoft SQL Query Analyzer and Microsoft
> Enterprise Manager.  My work is generally very tedious, mostly because
> MS software doesn't script very well.  I can bring my laptop into
> work, however, or install cygwin and work from those machines if I so
> desired.  Scripting and collecting data would be so much easier on a
> linux box.  Still, I know that MySQL is the SQL database preference on
> Linux systems and so I am having a difficult time finding anything
> that advertises itself being compatible with Microsoft SQL Server.
> Does it even matter?  Thank you for your help and I look forward to
> your input.
>
> Andrew Jackman.
> W7MEZ.

I worked in a similar environment in the past (back in my past life as a

Windows Admin) and found the best solution for me was to install Perl 
(the Windows version from ActiveState) on a server that had access to 
all the other servers.  As you probably know Perl is a cross platform 
language you can use as you administer any operating system.  In 
addition to the stock Perl code, there are also a bunch of Perl modules 
that are Windows specific that are useful for a ton of scenarios from 
user management to connecting to MS SQL databases (just as easily as you

would connect to a MySQL database in Linux).  The trick with those 
modules is that they can not run from a Linux box, they utilize the 
Windows libraries, so you need to install them on a Windows machine.

http://www.activestate.com/Products/activeperl/

Of course, Microsoft has now created their PowerShell or whatever to 
make things easer to script, but just like VBscript was before it, they 
are languages that you can only use on their platform.  In my opinion, 
if you don't know any of these languages, you might as well learn Perl, 
since you can use it on any OS.  Good luck!

Kevin
http://utahsysadmin.com/



------------------------------

Message: 4
Date: Wed, 2 Apr 2008 02:15:46 -0600
From: Jackman <kd7nyq at gmail.com>
Subject: Re: [sllug-members]: Microsoft SQL Server
To: "Salt Lake Linux Users Group Discussions"
	<sllug-members at sllug.org>
Message-ID:
	<79c119390804020115m4be611f1x878308e55d52892c at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

I rather like the idea of using Perl or unixODBC to handle my SQL
access needs, but I am a little confused on one point.  Both the Perl
DBI Interace and the unixODBC suite reference a DB Driver that is
needed before they can do anything.  I am still not sure how to go
about it with the Perl interface, but ODBC tells me that the MS driver
is commercial and that i have to go through a company to go about
getting it.  From a few places I get the driver resides on the server
that I wish to use.  Is the driver something that i need to worry
about?  I am mostly focussing on Perl at this point with DBI if it
changes the way that I get help.  Thanks again.

Andrew Jackman.
W7MEZ.

On Tue, Apr 1, 2008 at 8:20 PM, Doran L. Barton <fozz at xmission.com>
wrote:
> Not long ago, Jackman proclaimed...
>
> > Where I work, everything revolves around a row of very large servers
>  > with MS Windows NT running Microsoft SQL Server.  To connect to
this
>  > server, I use primarily Microsoft SQL Query Analyzer and Microsoft
>  > Enterprise Manager.  My work is generally very tedious, mostly
because
>  > MS software doesn't script very well.  I can bring my laptop into
>  > work, however, or install cygwin and work from those machines if I
so
>  > desired.  Scripting and collecting data would be so much easier on
a
>  > linux box.  Still, I know that MySQL is the SQL database preference
on
>  > Linux systems and so I am having a difficult time finding anything
>  > that advertises itself being compatible with Microsoft SQL Server.
>  > Does it even matter?  Thank you for your help and I look forward to
>  > your input.
>
>  It should be fairly straight forward to connect to a M$-SQL server
from
>  Perl (using the DBI module) or Java (using JDBC and/or Hibernate).
The
>  UnixODBC folks < http://www.unixodbc.org/ > can probably provide some
more
>  information about command-line utilities for more generic
interaction, but
>  if you're looking for the ability to automate/script queries and
other
>  database operations, I would highly recommend Perl+DBI.
>
>  --
>  Doran L. Barton <fozz at xmission.com> - Linux, Perl, Web, good fun, and
more!
>   "Auto Repair Service. Free Pick-up and delivery.  Try us once,
you'll
>   never go anywhere again."
>     -- Classified ad in newspaper
>
> ______________________________________________________________________
>  See http://www.sllug.org/ for latest SLLUG news, information, links.
>  Join SLLUG and other UT LUG members on irc.FreeNode.net channel #Utah
>  sllug-members at sllug.org
>  http://www.sllug.org/cgi-bin/mailman/listinfo/sllug-members
>
>


------------------------------

Message: 5
Date: Wed, 02 Apr 2008 09:14:13 -0600
From: Corey Edwards <tensai at zmonkey.org>
Subject: Re: [sllug-members]: Microsoft SQL Server
To: sllug-members at sllug.org
Message-ID: <1207149253.15091.63.camel at pheasant>
Content-Type: text/plain

On Wed, 2008-04-02 at 02:15 -0600, Jackman wrote:
> I rather like the idea of using Perl or unixODBC to handle my SQL
> access needs, but I am a little confused on one point.  Both the Perl
> DBI Interace and the unixODBC suite reference a DB Driver that is
> needed before they can do anything.  I am still not sure how to go
> about it with the Perl interface, but ODBC tells me that the MS driver
> is commercial and that i have to go through a company to go about
> getting it.  From a few places I get the driver resides on the server
> that I wish to use.  Is the driver something that i need to worry
> about?  I am mostly focussing on Perl at this point with DBI if it
> changes the way that I get help.  Thanks again.

The driver you need is DBD::Sybase. It's available in CPAN. The driver
for unixODBC is FreeTDS. Mine came in a package named libsybdb5 (that's
on Debian). For Java, you need the JTDS library.

Those packages provide the low level database driver. The higher level
libraries (DBI, JDBC, etc) load the drivers and connect to the database.
To connect using Perl, here's what you would do (based off my config, so
YMMV).

1. Install FreeTDS
2. Edit /etc/freetds/freetds.conf. Add a section for your database
   [myserver]
   host = myserver.example.com
   port = 1433
   tds version = 7.0
3. Connect using DBI.
   use DBI;
   my $dbh =
    DBI->connect('dbi:Sybase:server=myserver;database=mydb',$user,$pw);

I don't use any GUI tools, so I can't comment on that. I use Perl DBI
for scripts and I use Henplus for interactive queries. It's a Java CLI
query tool and works great.

Corey




------------------------------

Message: 6
Date: Wed, 02 Apr 2008 10:32:12 -0600
From: Kyle Waters <unum at unum5.org>
Subject: Re: [sllug-members]: Grub Error
To: Salt Lake Linux Users Group Discussions <sllug-members at sllug.org>
Message-ID: <47F3B50C.4090802 at unum5.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Can you share with us some more information. Which distribution do you 
have installed?  What does the grub config look like for the default 
boot option(figure this out by pushing 'e' on the grub menu).  Which 
live cd are you using?  Using the live cd run cfdisk and post the 
display from that here.

Kyle


------------------------------

______________________________________________________________________
See http://www.sllug.org/ for latest SLLUG news, information, links.
Join SLLUG and other UT LUG members on irc.FreeNode.net channel #Utah
sllug-members at sllug.org
http://www.sllug.org/cgi-bin/mailman/listinfo/sllug-members


End of sllug-members Digest, Vol 44, Issue 3
********************************************


More information about the sllug-members mailing list