Get rid of DataTable

[Jordan S.]

How can get rid of a DataTable instance?

Set it to null + call Dispose on it? Anything else? Is Dispose really
necessary given that the DataTable doesn't hold any resources (AFAIKT)?

Yes, I know there is no deterministic finalization - but I want to do my
best to tell the system that I'm done with the DataTable ... and the garbage
collector is free to have it's way with it.

Thanks.

[Ignacio Machin ( .NET/ C# MVP )]

On May 29, 11:38*am, "Jordan S." <[e-mail]:

How can get rid of a DataTable instance?

Set it to null + call Dispose on it? *Anything else? Is Dispose really
necessary given that the DataTable doesn't hold any resources (AFAIKT)?

Yes, I know there is no deterministic finalization - but I want to do my
best to tell the system that I'm done with the DataTable ... and the garbage
collector is free to have it's way with it.

Thanks.

Hi,

You can call Dispose if it implement it, and you can set it to null.
this will free the memory IF (and that's a capital if) it's not
referenced somewhere else,like for example in a DataSet

[Marc S]

On May 29, 12:03*pm, "Ignacio Machin ( .NET/ C# MVP )"
<[e-mail]:

On May 29, 11:38*am, "Jordan S." <[e-mail]:

How can get rid of a DataTable instance?

Set it to null + call Dispose on it? *Anything else? Is Dispose really
necessary given that the DataTable doesn't hold any resources (AFAIKT)?

Yes, I know there is no deterministic finalization - but I want to do my
best to tell the system that I'm done with the DataTable ... and the garbage
collector is free to have it's way with it.

Thanks.

Hi,

You can call Dispose if it implement it, and you can set it to null.
this will free the memory IF (and that's a capital if) it's not
referenced somewhere else,like for example in a DataSet

Then you can call

System.GC.Collect(); to force garbage collection.

[Ignacio Machin ( .NET/ C# MVP )]

On May 29, 3:08*pm, Marc S <[e-mail]:

On May 29, 12:03*pm, "Ignacio Machin ( .NET/ C# MVP )"

<[e-mail]:

On May 29, 11:38*am, "Jordan S." <[e-mail]:

How can get rid of a DataTable instance?

Set it to null + call Dispose on it? *Anything else? Is Dispose really
necessary given that the DataTable doesn't hold any resources (AFAIKT)?

Yes, I know there is no deterministic finalization - but I want to do my
best to tell the system that I'm done with the DataTable ... and the garbage
collector is free to have it's way with it.

Thanks.

Hi,

You can call Dispose if it implement it, and you can set it to null.
this will free the memory IF (and that's a capital if) it's not
referenced somewhere else,like for example in a DataSet

Then you can call

System.GC.Collect(); *to force garbage collection.- Hide quoted text -

- Show quoted text -

Unless you have a REAL justification I would leave the GC work his
magic alone

[=?ISO-8859-1?Q?Lasse_V=E5gs=E6ther_Karlsen?=]

Jordan S. wrote:

How can get rid of a DataTable instance?

Set it to null + call Dispose on it? Anything else? Is Dispose really
necessary given that the DataTable doesn't hold any resources (AFAIKT)?

Yes, I know there is no deterministic finalization - but I want to do my
best to tell the system that I'm done with the DataTable ... and the garbage
collector is free to have it's way with it.

Thanks.

General rule is to always call Dispose on objects that implement the
IDisposable pattern, when you're done with the object.

DataTable implements IDisposable since it inherits from
MarshalByRefComponent, and doesn't even override Dispose, so basically
the only code involved in IDisposable for a DataTable is what's in
MarshalByRefComponent.

Unless you have specific reasons for *not* calling Dispose, don't
second-guess what the code does and just call it.

--
Lasse Vågsæther Karlsen
mailto:la***@vkarlsen.no
http://presentationmode.blogspot.com/
PGP KeyID: 0xBCDEA2E3

[Marc S]

On May 29, 5:15*pm, "Ignacio Machin ( .NET/ C# MVP )"
<[e-mail]:

On May 29, 3:08*pm, Marc S <[e-mail]:

On May 29, 12:03*pm, "Ignacio Machin ( .NET/ C# MVP )"

<[e-mail]:

On May 29, 11:38*am, "Jordan S." <[e-mail]:

How can get rid of a DataTable instance?

Set it to null + call Dispose on it? *Anything else? Is Dispose really
necessary given that the DataTable doesn't hold any resources (AFAIKT)?

Yes, I know there is no deterministic finalization - but I want to do my
best to tell the system that I'm done with the DataTable ... and thegarbage
collector is free to have it's way with it.

Thanks.

Hi,

You can call Dispose if it implement it, and you can set it to null.
this will free the memory IF (and that's a capital if) it's not
referenced somewhere else,like for example in a DataSet

Then you can call

System.GC.Collect(); *to force garbage collection.- Hide quoted text -

- Show quoted text -

Unless you have a REAL justification I would leave the GC work his
magic alone- Hide quoted text -

- Show quoted text -

I would say that is correct. Unless you have a cheapie company that
has low end machines and your data tables are large wait for the
garbage collector to do its thing automatically. If you jsut really
want to for=ce everything to be scrubbed the option is there. I would
think by .NET 3.5 they would have all of the kinks worked out of
manual garbage collection but I haven't had to use it in a long time
since we have decent machines here and I have learned to slim down my
footprint.

[=?ISO-8859-1?Q?Lasse_V=E5gs=E6ther_Karlsen?=]

Marc S wrote:

On May 29, 5:15 pm, "Ignacio Machin ( .NET/ C# MVP )"
<[e-mail]:

>On May 29, 3:08 pm, Marc S <[e-mail]:

>>On May 29, 12:03 pm, "Ignacio Machin ( .NET/ C# MVP )"
<[e-mail]:
On May 29, 11:38 am, "Jordan S." <[e-mail]:
How can get rid of a DataTable instance?
Set it to null + call Dispose on it? Anything else? Is Dispose really
necessary given that the DataTable doesn't hold any resources (AFAIKT)?
Yes, I know there is no deterministic finalization - but I want to do my
best to tell the system that I'm done with the DataTable ... and the garbage
collector is free to have it's way with it.
Thanks.
Hi,
You can call Dispose if it implement it, and you can set it to null.
this will free the memory IF (and that's a capital if) it's not
referenced somewhere else,like for example in a DataSet
Then you can call
System.GC.Collect(); to force garbage collection.- Hide quoted text -
- Show quoted text -

Unless you have a REAL justification I would leave the GC work his
magic alone- Hide quoted text -

- Show quoted text -

I would say that is correct. Unless you have a cheapie company that
has low end machines and your data tables are large wait for the

I don't think you should need to manually call the garbage collector on
any machine at all.

The garbage collector registers with Windows for low-memory conditions,
and will, when needed, start to run more often if some other application
needs the memory. In other words, GC will run as often as required.

garbage collector to do its thing automatically. If you jsut really
want to for=ce everything to be scrubbed the option is there. I would
think by .NET 3.5 they would have all of the kinks worked out of
manual garbage collection but I haven't had to use it in a long time
since we have decent machines here and I have learned to slim down my
footprint.

--
Lasse Vågsæther Karlsen
mailto:la***@vkarlsen.no
http://presentationmode.blogspot.com/
PGP KeyID: 0xBCDEA2E3

[Marc S]

On May 30, 8:09*am, Lasse Vågsæther Karlsen <[e-mail]:

Marc S wrote:

On May 29, 5:15 pm, "Ignacio Machin ( .NET/ C# MVP )"
<[e-mail]:

On May 29, 3:08 pm, Marc S <[e-mail]:

>On May 29, 12:03 pm, "Ignacio Machin ( .NET/ C# MVP )"
<[e-mail]:
On May 29, 11:38 am, "Jordan S." <[e-mail]:
How can get rid of a DataTable instance?
Set it to null + call Dispose on it? *Anything else? Is Dispose really
necessary given that the DataTable doesn't hold any resources (AFAIKT)?
Yes, I know there is no deterministic finalization - but I want to do my
best to tell the system that I'm done with the DataTable ... and thegarbage
collector is free to have it's way with it.
Thanks.
Hi,
You can call Dispose if it implement it, and you can set it to null.
this will free the memory IF (and that's a capital if) it's not
referenced somewhere else,like for example in a DataSet
Then you can call
System.GC.Collect(); *to force garbage collection.- Hide quoted text-
- Show quoted text -
Unless you have a REAL justification I would leave the GC work his
magic alone- Hide quoted text -

- Show quoted text -

I would say that is correct. Unless you have a cheapie company that
has low end machines and your data tables are large wait for the

I don't think you should need to manually call the garbage collector on
any machine at all.

The garbage collector registers with Windows for low-memory conditions,
and will, when needed, start to run more often if some other application
needs the memory. In other words, GC will run as often as required.

garbage collector to do its thing automatically. *If you jsut really
want to for=ce everything to be scrubbed the option is there. *I would
think by .NET 3.5 they would have all of the kinks worked out of
manual garbage collection but I haven't had to use it in a long time
since we have decent machines here and I have learned to slim down my
footprint.

--
Lasse Vågsæther Karlsen
mailto:[e-mail]://presentationmode.blogspot.com/
PGP KeyID: 0xBCDEA2E3- Hide quoted text -

- Show quoted text -

See, when I was working in 1.1 that wasn't always true. The system did
a lot of swapping when it had dead objects it could clean up which is
why I did it back then. I would hope things are different now but I
haven't been forced to use it. I guess my thoughts are based on old
technology at this point.