[Mono-list] different behavior between .NET and Mono
Fri, 18 Feb 2005 10:11:44 -0500 (EST)
On Wed, February 16, 2005 5:00 pm, Dan Maltes said:
> You can use the user account in sql that already there for access to
> database, that's fine. However, the connection must authenticate you by
sending the username and password, whereas with windows authentication,
> logged in windows user credentials would be sent automatically, and the
matched against a sql user, which is what cannot happen on mono. So,
> your connection string could be altered to pass the sql user name and
I have added a new user and I'm using it from the .NET code and the Mono
Watching the MS-SQL profiler, I can see that both .NET and Mono are using
the SqlClient (ApplicationName column). The .NET event classes are all
RPC: Completed and the Mono event classes are SQL:BatchCompleted. The
issued commands are similar but not identical (.NET has more spaces in the
command and Mono prefixes "SelectReferenceTables" with "dbo.").
Before the SQL batch completed line which is indicated on my browser
screen as the statement which threw the exception is an "Audit Login"
I don't have any indications of errors in the Profiler log...
Is this possibly a bug in Mono?
> -----Original Message-----
> From: firstname.lastname@example.org
> [mailto:email@example.com] On Behalf Of Michael George
Sent: Wednesday, February 16, 2005 4:14 PM
> To: Dan Maltes
> Cc: 'Michael George'; 'A Rafael D Teixeira'; 'MonoList'
> Subject: RE: [Mono-list] different behavior between .NET and Mono
> On Wed, February 16, 2005 3:35 pm, Dan Maltes said:
>> Correct. And you will need to a create sql user(s) that have access to
that database. Then, the client app must use sql login instead of
> I'm not a pro at MS-SQL, though I'm kinda learning my way around...
> So there's a difference between an SQL user and a Windows users? I have
> users: Xuser with no Login Name and Permit DB access, and dbo with a
> Name of Xuser and Permit DB access. Looking at either users'
> don't see how to know which type of user they are.
> As for the type of login, I'm guessing that will be part of the options
> the connection call rather than the connection string? I don't see
> that indicates the type of connection in the connection string...
> However, since the SQL logging output indicates SQL commands being
> it seems that it already knows to use an SQL connection.
> Thank you very much!
>> From: firstname.lastname@example.org
>> [mailto:email@example.com] On Behalf Of Michael George
Sent: Wednesday, February 16, 2005 3:19 PM
>> To: A Rafael D Teixeira
>> Cc: Michael George; MonoList
>> Subject: Re: [Mono-list] different behavior between .NET and Mono On
Wed, February 16, 2005 2:42 pm, A Rafael D Teixeira said:
>>> AFAIK, our ADO.NET provider for SQLServer (it is part of Mono) only
can connect with SQL password, as the other protocol is a closed one
that ties with ActiveDirectory and/or NT Domain Controllers.
>>> Configure your database server to accept SQL connections, otherwise we
can't connect to it.
>> Looking at the properties for my database, the Security tab, under
Authentication I have "SQL Server and Windows" set. I think that's
what you're saying to do, right?
>> -Michael George
>> Ideal Solution, LLC
>> Mono-list maillist - Monofirstname.lastname@example.org
> -Michael George
> Ideal Solution, LLC
> Mono-list maillist - Monoemail@example.com
Ideal Solution, LLC