FreeTDS Development Group

[brian AT bruns.com]

FreeTDS does not support named pipes.  If you can turn us on to a nice
LGPL DCE/RPC library, maybe that'll change.

For network traces, try out Ethereal (www.ethereal.org) they have a
Windows port.  That will require the data is actually flowing over the
network though, and not on the same machine.

Brian

On Mon, 5 Jul 2004 17:09:24 -0400, "Daniel Morgan" wrote:

> 
> How would I do a network trace on Windows XP Pro?
> 
> My original question was asking how to connect to the new SQL 2005
> Express Beta.
> 
> I didn't know if the TDS protocol needed updating or what.  I knew
you
> guys knew TDS.  Basically, I didn't know enough to ask the right
> question.
> 
> Currently:
> - can connect via Query Analyzer that comes with SQL 2000 Developer
> using NT Auth.
> - unable to connect via Enterprise Manager that comes with SQL 2000
> Developer ( I think this is mentioned in the release notes you can't
> do)
> - unable to connect via Mono's SqlClient either way: SQL Auth nor NT
> Auth
> - someone mentioned (Peter Ducan ?) said they can connect via
FreeTDS.
> He didn't say what he did to connect.
> 
> I have only been trying to connect on my local machine.  So, I wonder
> what I am doing wrong then.
> 
> Does FreeTDS support connecting via named pipes?
> 
> Daniel
> 
> -----Original Message-----
> From: freetds-bounces AT lists.ibiblio.org
> [mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of
brian AT bruns.com
> Sent: Wednesday, June 30, 2004 11:47 PM
> To: freetds AT lists.ibiblio.org
> Subject: Re: [freetds] Microsoft SQL Server 2005 Express Beta 1
> 
> 
> My point is, I guess, that they seem to be targeting this to the
niche
> that Jet (Access) currently fulfills. Single machine or small
workgroup
> database.  Look to see Access frontend to this instead of Jet with
the
> next major rev (my supposition).
> 
> Glad to see tcpip/tds can be reenabled on this beast.  But, my point
is
> that you'll start seeing MSDE/SSE files distributed in the same
manner
> that Jet files are today within the next couple of years.  Same
> underlying technology, maybe, but different market space.  FreeTDS
> won't
> do the job when someone sends you one of these in the ol' email.
> 
> Thinking about it, I'm not quite sure that I understood the original
> post.  Did you mean that other machines can access the server, but
only
> from CLI? or it is accessible on the same machine only through CLI? 
If
> it's going across networks than it must be named pipes? Or perhaps it
> is
> DCOM?  Would be interesting to get a network trace in that case.
> 
> Cheers,
> 
> Brian
> 
> On Wed, 30 Jun 2004 22:41:41 -0400, "James K. Lowden" wrote:
> 
> > 
> > On Wed, 30 Jun 2004, brian AT bruns.com wrote:
> > > I don't consider this a huge issue, as this is a replacement for
> MSDE
> > > which is more of an Access replacement than something in the SQL 
> > > Server line.  They are just trying to leverage SQL Server name,
> > IMNSHO
> > 
> > Is that really the case, Brian?  I mean, Access isn't exactly an 
> > unknown brand itself, but, more important, it speaks a different 
> > dialect of SQL.
> > AIUI (and allowing for some marketing hyperbole) SS2K5E is a
drop-in
> > T-SQL
> > replacement for good ol' SQL Server.  It has stored procedures,
> > triggers,
> > views.  Access has all that?  
> > 
> > The real question would be, can it be a multi-user database?  Is
> there
> > security and isolation?  Is the whole user/group/role
implementation 
> > there; do tables have owners and permissions that attach to them?
> > 
> > If it's multi-user and merely lacking a remote-access protocol (no
> pun
> > intended), then frontending it with our server would be a cool and 
> > useful hack IMO.  OTOH, if it doesn't have those things, nothing
we 
> > can do will
> > fix it.  
> > 
> > --jkl
> > _______________________________________________
> > FreeTDS mailing list
> > FreeTDS AT lists.ibiblio.org 
> > http://lists.ibiblio.org/mailman/listinfo/freetds
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds
> 
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds