MDF

I have a system in Vb using SQL 2000.
happens that MDF has + - 400 mdf mb. And LDF increases reaching 2 Gb in 1
w a lot!
Does have as creating a routine for everyday to reduce the space of this
file?
Manually, I make the backup log <name table> with truncate only.. and later
I make the shrink database!
An option exists in Enterprise Manager of <Database Maintenance Plans> where
configures the maintenances (backup, shrink, etc)... I Made the tests and it
didn't reduce the size! IS THIS THE CORRECT OPTION FOR THIS?Hi
You can create a maintenance plan to do this, or alternatively craft your
own ot use sqlmaint without an existing plan.
If you log file is not shrinking then check out:
http://msdn.microsoft.com/library/d...r />
_1uzr.asp
John
"Frank Dulk" <fdulk@.bol.com.br> wrote in message
news:uinlXfLLFHA.3064@.TK2MSFTNGP12.phx.gbl...
>I have a system in Vb using SQL 2000.
> happens that MDF has + - 400 mdf mb. And LDF increases reaching 2 Gb in 1
> w a lot!
> Does have as creating a routine for everyday to reduce the space of this
> file?
> Manually, I make the backup log <name table> with truncate only.. and
> later
> I make the shrink database!
> An option exists in Enterprise Manager of <Database Maintenance Plans>
> where
> configures the maintenances (backup, shrink, etc)... I Made the tests and
> it
> didn't reduce the size! IS THIS THE CORRECT OPTION FOR THIS?
>

MDAC 2.8 seems cause SQL backup fail, can anyone send us a MDAC 2.8 latest hotfix ?

Dear all,
After our team has upgraded backup software of one server to "Veritas
BackupExec 9.1",
We found our routine SQL backup jobs (as part of our maintenance plan) fail
on it.
From our investigation, we suspect it is caused by the MDAC 2.8 installed
with BackupExec 9.1
The problem seems already documented in microsoft support article :
http://support.microsoft.com/defaul...kb;en-us;827452
However, as our company has not join MS support service, I have no formal
channel
to receive hot fix for the MDAC.
(Actually the article suggest to update dbnmpntw.dll to a version after
09-17-2003 (2000.85.1022.42),
but it is already 2 years but still no MDAC 2.8 SP1 out there, which is
quite disappointed)
Can anyone give me a hand ?
Thanks for anyone's kind help in advance ... EricSorry, I forget to mention my environment.
Our server is running Win2000 Std Server (English) with SP3.
"Eric Fung" <Pls type eric.fung plus @.hld.com> bl
news:uQ$IZf0PFHA.244@.TK2MSFTNGP12.phx.gbl g...
> Dear all,
> After our team has upgraded backup software of one server to "Veritas
> BackupExec 9.1",
> We found our routine SQL backup jobs (as part of our maintenance plan)
fail
> on it.
> From our investigation, we suspect it is caused by the MDAC 2.8 installed
> with BackupExec 9.1
> The problem seems already documented in microsoft support article :
> http://support.microsoft.com/defaul...kb;en-us;827452
> However, as our company has not join MS support service, I have no formal
> channel
> to receive hot fix for the MDAC.
> (Actually the article suggest to update dbnmpntw.dll to a version after
> 09-17-2003 (2000.85.1022.42),
> but it is already 2 years but still no MDAC 2.8 SP1 out there, which
is
> quite disappointed)
> Can anyone give me a hand ?
> Thanks for anyone's kind help in advance ... Eric
>|||Eric wrote on Tue, 12 Apr 2005 18:10:10 +0800:

> However, as our company has not join MS support service, I have no formal
> channel
> to receive hot fix for the MDAC.
You don't need to "join" the support service. Just ring the service number
for your country, explain the issue, and they send you a location to
download the fix from and a password to access the download. So long as it's
an issue covered by the article that requires a file(s) from MS support they
won't charge.
Dan|||Dear Daniel,
Thanks a lot for your advice, I will try.
Eric
"Daniel Crichton" <msnews@.worldofspack.co.uk> bl
news:udnoPP3PFHA.2584@.TK2MSFTNGP15.phx.gbl g...
> Eric wrote on Tue, 12 Apr 2005 18:10:10 +0800:
>
formal[vbcol=seagreen]
> You don't need to "join" the support service. Just ring the service number
> for your country, explain the issue, and they send you a location to
> download the fix from and a password to access the download. So long as
it's
> an issue covered by the article that requires a file(s) from MS support
they
> won't charge.
> Dan
>sql

MDAC 2.8 seems cause SQL backup fail, can anyone send us a MDAC 2.8 latest hotfix ?

Dear all,
After our team has upgraded backup software of one server to "Veritas
BackupExec 9.1",
We found our routine SQL backup jobs (as part of our maintenance plan) fail
on it.
From our investigation, we suspect it is caused by the MDAC 2.8 installed
with BackupExec 9.1
The problem seems already documented in microsoft support article :
http://support.microsoft.com/default...b;en-us;827452
However, as our company has not join MS support service, I have no formal
channel
to receive hot fix for the MDAC.
(Actually the article suggest to update dbnmpntw.dll to a version after
09-17-2003 (2000.85.1022.42),
but it is already 2 years but still no MDAC 2.8 SP1 out there, which is
quite disappointed)
Can anyone give me a hand ?
Thanks for anyone's kind help in advance ... Eric
Sorry, I forget to mention my environment.
Our server is running Win2000 Std Server (English) with SP3.
"Eric Fung" <Pls type eric.fung plus @.hld.com> bl
news:uQ$IZf0PFHA.244@.TK2MSFTNGP12.phx.gbl g...
> Dear all,
> After our team has upgraded backup software of one server to "Veritas
> BackupExec 9.1",
> We found our routine SQL backup jobs (as part of our maintenance plan)
fail
> on it.
> From our investigation, we suspect it is caused by the MDAC 2.8 installed
> with BackupExec 9.1
> The problem seems already documented in microsoft support article :
> http://support.microsoft.com/default...b;en-us;827452
> However, as our company has not join MS support service, I have no formal
> channel
> to receive hot fix for the MDAC.
> (Actually the article suggest to update dbnmpntw.dll to a version after
> 09-17-2003 (2000.85.1022.42),
> but it is already 2 years but still no MDAC 2.8 SP1 out there, which
is
> quite disappointed)
> Can anyone give me a hand ?
> Thanks for anyone's kind help in advance ... Eric
>
|||Eric wrote on Tue, 12 Apr 2005 18:10:10 +0800:

> However, as our company has not join MS support service, I have no formal
> channel
> to receive hot fix for the MDAC.
You don't need to "join" the support service. Just ring the service number
for your country, explain the issue, and they send you a location to
download the fix from and a password to access the download. So long as it's
an issue covered by the article that requires a file(s) from MS support they
won't charge.
Dan
|||Dear Daniel,
Thanks a lot for your advice, I will try.
Eric
"Daniel Crichton" <msnews@.worldofspack.co.uk> bl
news:udnoPP3PFHA.2584@.TK2MSFTNGP15.phx.gbl g...[vbcol=seagreen]
> Eric wrote on Tue, 12 Apr 2005 18:10:10 +0800:
formal
> You don't need to "join" the support service. Just ring the service number
> for your country, explain the issue, and they send you a location to
> download the fix from and a password to access the download. So long as
it's
> an issue covered by the article that requires a file(s) from MS support
they
> won't charge.
> Dan
>

MDAC 2.8 seems cause SQL backup fail, can anyone send us a MDAC 2.8 latest hotfix ?

Dear all,
After our team has upgraded backup software of one server to "Veritas
BackupExec 9.1",
We found our routine SQL backup jobs (as part of our maintenance plan) fail
on it.
From our investigation, we suspect it is caused by the MDAC 2.8 installed
with BackupExec 9.1
The problem seems already documented in microsoft support article :
http://support.microsoft.com/default.aspx?scid=kb;en-us;827452
However, as our company has not join MS support service, I have no formal
channel
to receive hot fix for the MDAC.
(Actually the article suggest to update dbnmpntw.dll to a version after
09-17-2003 (2000.85.1022.42),
but it is already 2 years but still no MDAC 2.8 SP1 out there, which is
quite disappointed)
Can anyone give me a hand ?
Thanks for anyone's kind help in advance ... EricSorry, I forget to mention my environment.
Our server is running Win2000 Std Server (English) with SP3.
"Eric Fung" <Pls type eric.fung plus @.hld.com> ¦b¶l¥ó
news:uQ$IZf0PFHA.244@.TK2MSFTNGP12.phx.gbl ¤¤¼¶¼g...
> Dear all,
> After our team has upgraded backup software of one server to "Veritas
> BackupExec 9.1",
> We found our routine SQL backup jobs (as part of our maintenance plan)
fail
> on it.
> From our investigation, we suspect it is caused by the MDAC 2.8 installed
> with BackupExec 9.1
> The problem seems already documented in microsoft support article :
> http://support.microsoft.com/default.aspx?scid=kb;en-us;827452
> However, as our company has not join MS support service, I have no formal
> channel
> to receive hot fix for the MDAC.
> (Actually the article suggest to update dbnmpntw.dll to a version after
> 09-17-2003 (2000.85.1022.42),
> but it is already 2 years but still no MDAC 2.8 SP1 out there, which
is
> quite disappointed)
> Can anyone give me a hand ?
> Thanks for anyone's kind help in advance ... Eric
>|||Eric wrote on Tue, 12 Apr 2005 18:10:10 +0800:
> However, as our company has not join MS support service, I have no formal
> channel
> to receive hot fix for the MDAC.
You don't need to "join" the support service. Just ring the service number
for your country, explain the issue, and they send you a location to
download the fix from and a password to access the download. So long as it's
an issue covered by the article that requires a file(s) from MS support they
won't charge.
Dan|||Dear Daniel,
Thanks a lot for your advice, I will try.
Eric
"Daniel Crichton" <msnews@.worldofspack.co.uk> ¦b¶l¥ó
news:udnoPP3PFHA.2584@.TK2MSFTNGP15.phx.gbl ¤¤¼¶¼g...
> Eric wrote on Tue, 12 Apr 2005 18:10:10 +0800:
> > However, as our company has not join MS support service, I have no
formal
> > channel
> > to receive hot fix for the MDAC.
> You don't need to "join" the support service. Just ring the service number
> for your country, explain the issue, and they send you a location to
> download the fix from and a password to access the download. So long as
it's
> an issue covered by the article that requires a file(s) from MS support
they
> won't charge.
> Dan
>