Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

database interfaces in powerbuilder 10

132 views
Skip to first unread message

tashfinwahid

unread,
Aug 27, 2004, 4:42:30 PM8/27/04
to
I installed powerbuilder 10 with the default configurations.
When I went to connect to my microsoft sql server database,
I noticed that 10 didnt have a MSS Microsoft SQL Server
database interface. How do I add it? Did I miss a selection
during installation?

Please email back at

wah...@friedfrank.com

Thanks,
Tashfin Wahid

Doug Porter

unread,
Aug 27, 2004, 4:50:09 PM8/27/04
to
As far as I know, for 10 you would use the ADO.net driver to connect to MS
Sql Server. That is the way the MS is going for their database
connectivity, so no native driver included. So you would create a
datasource on your local machine and configure the ADO.net driver to use
that datasource.

Doug

<Tashfin Wahid> wrote in message news:412f9e2f.723...@sybase.com...

Jim O'Neil [Sybase]

unread,
Aug 27, 2004, 6:08:50 PM8/27/04
to
Actually, I'd go for the OLE-Db driver. PB's ADO.NET is another layer
on that.

For info on the reason the MSS driver is not shipped, take a look at:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/bldgapps/ba_highprog_56pc.asp

The MSS driver uses the DB-Library DLLs that are referred to in this
article (the ones at the old TDS 4.2) level, so you can see the
obvious limitations.


On 27 Aug 2004 13:50:09 -0700, "Doug Porter"

Tyler Cruse

unread,
Aug 28, 2004, 8:30:23 PM8/28/04
to
I agree with Jim that ADO.NET is more layers. Now with that said, I have
two testers that claim that when I configure a
ADO instead of OLE_DB that the performance is better. Apparently, the extra
layer is providing a "caching" function that actually
provides a "faster experience" for the end user.

The only negative that I know of on ADO.NET is the timeout for queries that
is set at 30 seconds. So, if you have any long
running queries (e.g. reports) that take over 30 seconds, your are SOL with
ADO.net. I think this behavior is a bug and reported it as such
during the beta, however, it was not fixed in 4510. I would not be suprised
to see it fixed in some future EBF build.

OLE-DB to SQL server 2000 SP3a is working well. I also have a test database
on Yukon beta2 and that is also doing well also.

I have received some e-mails indicating that build 5013 has a two of my beta
bugs resolved, however, I do not recall
if the ADO isssue was one of them.

"Jim O'Neil [Sybase]" <joneil_at_sybase_dot_com> wrote in message
news:dgbvi0thlrb72g75b...@4ax.com...

0 new messages