FreeTDS Development Group

[brian AT bruns.com]

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