my ADO-Toolkit for LabVIEW 8

[i2dx]

Finally, I have an Update for you:

ADO-Toolkit V 1.6.3

I would be glad, If you give it a chance

[i2dx]

Guy's, I'd really like to thank you!

The ADO-Toolkit Downloads reached a new maximum in February:

471 DOWNLOADS in one month!

I'm glad that you like my tool - this is a great encouragement to keep on developing and improving!

[Mike Ashe]

Very nice! Thanks again for contributing this to the community. I think the license change to Creative Commons was a great move. To really get a package wide acceptance I think it needs either BSD or Creative Commons licensing these days.

:thumbup:

[i2dx]

QUOTE(Mike Ashe @ Mar 12 2007, 08:48 PM)

Very nice! Thanks again for contributing this to the community. I think the license change to Creative Commons was a great move. To really get a package wide acceptance I think it needs either BSD or Creative Commons licensing these days.

:thumbup:

thanks

yes, I think the CC is the right license, because most users do not want to be forced to publish their code as Open Source and I don't want to force anyone to use a specific license.

[alukindo]

isdx:

I have noticed memory leaks in ADO <Connection Execute> method when used with repeated SQL or Stored Procedure calls on SQL Server. The Connection Object <Create Method> may help resolve this if the property settings shown on the attachment are included. I figured that the connection object <Connection Execute> method also runs faster when this is done. I have seen memory leaks especially with large insert SQL queries.

.... Any thoughts on your experience with memory leaks and ways to resolve the same?

Anthony Lukindo

[i2dx]

QUOTE(alukindo @ Mar 22 2007, 08:58 PM)

isdx:

I have noticed memory leaks in ADO <Connection Execute> method when used with repeated SQL or Stored Procedure calls on SQL Server. The Connection Object <Create Method> may help resolve this if the property settings shown on the attachment are included. I figured that the connection object <Connection Execute> method also runs faster when this is done. I have seen memory leaks especially with large insert SQL queries.

.... Any thoughts on your experience with memory leaks and ways to resolve the same?

Anthony Lukindo

hmm, it's the first time someone is reporting a memory leak, I never got bug reports in this direction before. I'll start a search at the MSDN, maybe there is a known issue with ADO and SQL Server, but it may take a while. Therefore I have no solution at the moment.

Maybe you can check, if you have installed the latest version of MDAC? MDAC 2.8 is the current version, and if we are lucky, this issue is allready solved

[alukindo]

Hi i2dx:

Thanks for helping to follow-up on this. Yes, I have ADO 2.8. and I made sure that I reference the connection object from this latest library. The applications I run make SQL calls every 5 seconds or so and the connection remains open all along. I was suspecting that the cursor type used when a connection is opened without any property settings is one with a high overhead. The recordest returned is the one that may carry this overhead. I have also tried closing the connection after each SQL call but the results are the same.

... For less frequent SQL calls and for queries that insert values in few columns (2 to 3) the memory leak problem is not noticeable. If you insert to something like 12 to 24 columns then it is more prevalent.

Thanks

Anthony Lukindo

[i2dx]

QUOTE(alukindo @ Mar 23 2007, 04:51 AM)

Hi i2dx:

Thanks for helping to follow-up on this. Yes, I have ADO 2.8. and I made sure that I reference the connection object from this latest library. The applications I run make SQL calls every 5 seconds or so and the connection remains open all along. I was suspecting that the cursor type used when a connection is opened without any property settings is one with a high overhead. The recordest returned is the one that may carry this overhead. I have also tried closing the connection after each SQL call but the results are the same.

... For less frequent SQL calls and for queries that insert values in few columns (2 to 3) the memory leak problem is not noticeable. If you insert to something like 12 to 24 columns then it is more prevalent.

Thanks

Anthony Lukindo

ok, that's really strange. I have an application (written with ADO Toolkit 1.5.x and LV 7.1.1) running at my customer, which is a "DB Proxy" where up to 30 Clients connect via TCP/IP and send up to 60 (peak) SQL-Queries (SELECT, INSERT, UPDATE) per cecond. I have implementet all Queries as Stored Procedures on the MS SQL Server and I did not experience a memory leak. The DB connection is open from "Server Start" till "Server Shutdown" ...

Which LV Version are you using, and which Version of the ADO-Toolkit? Please make sure, that you are using the latest version, because I will only debug (of course) the latest one

[i2dx]

ok, I just tried it out, and I can not find a memory leak:

I have used this vi: http://forums.lavag.org/index.php?act=attach&type=post&id=5267 on LV 8.2, with ADO-Tool 1.6.3 for LV 8.2

Memory usage before the start:

http://forums.lavag.org/index.php?act=attach&type=post&id=5268

Menory usage while running:

http://forums.lavag.org/index.php?act=attach&type=post&id=5269

Memory usage the VI finished:

http://forums.lavag.org/index.php?act=attach&type=post&id=5270

I have inserted 5000 rows at 20 Hz and there was no significant increase of the used memory during the VIs run.

This is the table, I inserted in:

QUOTE

USE [test]

GO

/****** Objekt: Table [dbo].[tbl_tdata] Skriptdatum: 03/23/2007 08:22:34 ******/

SET ANSI_NULLS ON

GO

SET QUOTED_IDENTIFIER ON

GO

SET ANSI_PADDING ON

GO

CREATE TABLE [dbo].[tbl_tdata](

[id_tdata] [int] IDENTITY(1,1) NOT NULL,

[nf1] [float] NOT NULL CONSTRAINT [DF_tbl_tdata_nf1] DEFAULT ((-1)),

[nf2] [float] NOT NULL CONSTRAINT [DF_tbl_tdata_nf2] DEFAULT ((-1)),

[nf3] [float] NOT NULL CONSTRAINT [DF_tbl_tdata_nf3] DEFAULT ((-1)),

[nf4] [float] NOT NULL CONSTRAINT [DF_tbl_tdata_nf4] DEFAULT ((-1)),

[nf5] [float] NOT NULL CONSTRAINT [DF_tbl_tdata_nf5] DEFAULT ((-1)),

[nf6] [float] NOT NULL CONSTRAINT [DF_tbl_tdata_nf6] DEFAULT ((-1)),

[nf7] [float] NOT NULL CONSTRAINT [DF_tbl_tdata_nf7] DEFAULT ((-1)),

[nf8] [float] NOT NULL CONSTRAINT [DF_tbl_tdata_nf8] DEFAULT ((-1)),

[nf9] [float] NOT NULL CONSTRAINT [DF_tbl_tdata_nf9] DEFAULT ((-1)),

[nf10] [float] NOT NULL CONSTRAINT [DF_tbl_tdata_nf10] DEFAULT ((-1)),

[st11] [varchar](100) NOT NULL CONSTRAINT [DF_tbl_tdata_st11] DEFAULT ('void'),

[st12] [varchar](100) NOT NULL CONSTRAINT [DF_tbl_tdata_st12] DEFAULT ('void'),

[st13] [varchar](100) NOT NULL CONSTRAINT [DF_tbl_tdata_st13] DEFAULT ('void'),

[st14] [varchar](100) NOT NULL CONSTRAINT [DF_tbl_tdata_sr14] DEFAULT ('void'),

[st15] [varchar](100) NOT NULL CONSTRAINT [DF_tbl_tdata_st15] DEFAULT ('void'),

[st16] [varchar](100) NOT NULL CONSTRAINT [DF_tbl_tdata_st16] DEFAULT ('void'),

[st17] [varchar](100) NOT NULL CONSTRAINT [DF_tbl_tdata_st17] DEFAULT ('void'),

[st18] [varchar](100) NOT NULL CONSTRAINT [DF_tbl_tdata_st18] DEFAULT ('void'),

[st19] [varchar](100) NOT NULL CONSTRAINT [DF_tbl_tdata_st19] DEFAULT ('void'),

[st20] [varchar](100) NOT NULL CONSTRAINT [DF_tbl_tdata_st20] DEFAULT ('void')

) ON [PRIMARY]

GO

SET ANSI_PADDING OFF

Can you please use the attached VI, run this test on your machine and tell me the results? Maybe you have noticed the "sawtooth" in the CPU usage. The increase of the CPU-load occurs, when a memory block is freed ...

[alukindo]

Hi i2dx:

You have documented compelling evidence that the memory leak is non-existent in your application. I will do the same with your latest tool-kit and verify the case in my situation. Thanks for the useful test details!

Anthony

[Val Brown]

QUOTE(i2dx @ Jan 11 2006, 04:57 AM)

there is a new version of my ADO-Toolkit availiable. I made it for LabVIEW 8, because the "date time" cluster contains now a new element for fractional seconds. I don't use fractional seconds, but i wanted to get rid of the warnings and coercion dots ;-). There have been many improvements since my first post here, especially the documentation.

Maybe someone can help me with the palettes? I still could not figure out, how i can get rid of the "additional columns" in the palette view. I can delete them, and they are gone in edit mode, but they are there again after saving

Ah, there is an example for download on my homepage, if you are interested, and a version for LabVIEW 7.1, too ...

installation is simple: just extract the zip file to your vi.lib/addons folder, restart LabVIEW and you sould find the VIs in the Addons palette.

thx! i would be glad, if you find it usefull (amusing, or a nice toy) and feedback is allways wellcome!

http://forums.lavag.org/index.php?act=attach&type=post&id=1933''>http://forums.lavag.org/index.php?act=attach&type=post&id=1933'>http://forums.lavag.org/index.php?act=attach&type=post&id=1933

Is this ADO_Tool.LV80.zip still the latest version? I'm using LV8.2.

[i2dx]

QUOTE(Val Brown @ Mar 24 2007, 02:19 AM)

Is this ADO_Tool.LV80.zip still the latest version? I'm using LV8.2.

no, 1.6.3 is the current version for LV 8.2

You can get the newest version by clicking at the link in my signature ... now I have an english information and download page, too (BTW: if someone of the native speakers finds errors in the text, please let me know - and I am searching for a volunteer to correct the manual [yes, I really have startet and I am on page 10 ])

If you want to stay informed, you can register at my forum (the link is on the download page) and subscribe to the pinned topic in the http://forum.ib-berger.com/index.php?showforum=12' target="_blank">ADO-Toolkit forum. I'll announce all new versions in this thread, so you'll get an email automatically, if there are news regarding the ADO-Toolkit.