Database Memory

Hi,
I'm wondering, is there any option/tool that could let me
monitor a database's memory. There's a maximum amount
that we can allow, and it would be nice to have some kind
of alarm/warning message that would tell us we're at our
maximum, or close to it.
Thank you kindly.
MarcIf your DB is SQL Server, take a look at or
http://msdn.microsoft.com/library/en-us/adminsql/ad_mon_perf_76cm.asp. (or
in Books On-Line under Administering SQL Server .. Choosing a Monitoring
Tool). System Monitor (formerly PerfMon) supports sending alerts if a
threshold is exceeded. If you want to home grow your own, take a look at
the sp_monitor stored proc (in master DB) by running sp_helptext
"sp_monitor" .
--
-- "This posting is provided 'AS IS' with no warranties, and confers no
rights."
jhmiller@.online.microsoft.com
"Marc" <anonymous@.discussions.microsoft.com> wrote in message
news:1b6601c4a19e$0f77f140$a401280a@.phx.gbl...
> Hi,
> I'm wondering, is there any option/tool that could let me
> monitor a database's memory. There's a maximum amount
> that we can allow, and it would be nice to have some kind
> of alarm/warning message that would tell us we're at our
> maximum, or close to it.
> Thank you kindly.
> Marcsql

Database Maintenence Plan Error

When trying to setup a Database Maintenence Plan, it does not give me
an option for amount of days to keep before deleting, the dropdown box
is empty. also, I set the UNC path and when I go out and come back
into the plan, this is empty, but the backup runs with 17055 errors.
How can I find out how to correct this?
RickRick,
What build of SQL2005 are you running?
Chris
"Rick" <drummer10980@.gmail.com> wrote in message
news:1189777049.876020.129450@.y42g2000hsy.googlegroups.com...
> When trying to setup a Database Maintenence Plan, it does not give me
> an option for amount of days to keep before deleting, the dropdown box
> is empty. also, I set the UNC path and when I go out and come back
> into the plan, this is empty, but the backup runs with 17055 errors.
> How can I find out how to correct this?
> Rick
>|||Actually running MSDE
Rick
On Sep 14, 9:52 am, "Chris Wood" <anonym...@.microsoft.com> wrote:
> Rick,
> What build of SQL2005 are you running?
> Chris
> "Rick" <drummer10...@.gmail.com> wrote in message
> news:1189777049.876020.129450@.y42g2000hsy.googlegroups.com...
>
> > When trying to setup a Database Maintenence Plan, it does not give me
> > an option for amount of days to keep before deleting, the dropdown box
> > is empty. also, I set the UNC path and when I go out and come back
> > into the plan, this is empty, but the backup runs with 17055 errors.
> > How can I find out how to correct this?
> > Rick- Hide quoted text -
> - Show quoted text -

Database Maintenance

I have a maintenance plan set up to:
Remove unused space from database files
Shrink database when it grows beyond: 50 MB
Amount of free space to remain after shrink = 10%
Does this effect log files or just data files, or both?
--
Message posted via http://www.sqlmonster.comboth.
Many DBA's would not recommend shrinking the Database unless you
specifically are running into storage space issues.
My personal recommendation is that you disable this feature.
Greg Jackson
PDX, Oregon|||The maintenance plan will do a dbcc shrinkdatabase, not a
dbcc shrinkfile. As Greg posted, you really don't need this
in a regular maintenance plan. It's better to just size your
files appropriately and let them have the space they may
need for your normal operations. If they grow and you shrink
them and then they grow again right after you shrink them,
you just waste resources. Also, I think the maintenance plan
defaults to where you do a dbreindex and then a
shrinkdatabase. In that scenario, you likely just
reintroduce the fragmentation you cleaned up with the
dbreindex.
The following article on Tibor Karaszi's site had some
additional information on shrinking:
http://www.karaszi.com/sqlserver/info_dont_shrink.asp
-Sue
On Tue, 08 Feb 2005 22:21:42 GMT, "Robert Richards via
SQLMonster.com" <forum@.SQLMonster.com> wrote:
>I have a maintenance plan set up to:
>Remove unused space from database files
> Shrink database when it grows beyond: 50 MB
> Amount of free space to remain after shrink = 10%
>Does this effect log files or just data files, or both?|||I have applied "autoshrink" to many of my databases specifically= to try and keep the size of the logs down, and it seems to help.= I had much trouble with logs growinbg larger than the database,= but this has improved with autoshrink and nightly log backups.
> I have a maintenance plan set up to:
> Remove unused space from database files
> Shrink database when it grows beyond: 50 MB
> Amount of free space to remain after shrink =3D 10%
> Does this effect log files or just data files, or both?
> --
> Message posted via http://www.sqlmonster.com
User submitted from AEWNET (http://www.aewnet.com/)|||http://www.karaszi.com/SQLServer/info_dont_shrink.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"engel1" <engel1@.aew_nospam.com> wrote in message news:OE6hmHxEFHA.4004@.tk2msftngp13.phx.gbl...
I have applied "autoshrink" to many of my databases specifically to try and keep the size of the
logs down, and it seems to help. I had much trouble with logs growinbg larger than the database, but
this has improved with autoshrink and nightly log backups.
> I have a maintenance plan set up to:
> Remove unused space from database files
> Shrink database when it grows beyond: 50 MB
> Amount of free space to remain after shrink = 10%
> Does this effect log files or just data files, or both?
> --
> Message posted via http://www.sqlmonster.com
User submitted from AEWNET (http://www.aewnet.com/)

Database log files

Does anyone know of anyway to read the transaction logs? The reason why I am
curios is, the transaction logs are way to large for the amount of
transactions we are running(yes, the transaction logs are set to
automatically grow). Our application would not send that amount of
transactions to the database. The other thing I am thinking is that there is
another db within this sqlserver that I think access this DB and I think the
transaction logs would prove this.
Thanks for your assistance in advance....
I've listed three log reader tools on my links page:
http://www.karaszi.com/SQLServer/links.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"TJ" <TJ@.discussions.microsoft.com> wrote in message
news:92CF3A8E-4DA0-4E1B-BCA8-EC4491DCAFED@.microsoft.com...
> Does anyone know of anyway to read the transaction logs? The reason why I am
> curios is, the transaction logs are way to large for the amount of
> transactions we are running(yes, the transaction logs are set to
> automatically grow). Our application would not send that amount of
> transactions to the database. The other thing I am thinking is that there is
> another db within this sqlserver that I think access this DB and I think the
> transaction logs would prove this.
> Thanks for your assistance in advance....
|||What recovery mode are you in? If it is FULL and you don't issue regular
Log backups it will continue to grow and grow. Change it to simple mode and
you should not see it grow any more. If you really want to see what is
happening on the server you should use Profiler or Trace.
Andrew J. Kelly SQL MVP
"TJ" <TJ@.discussions.microsoft.com> wrote in message
news:92CF3A8E-4DA0-4E1B-BCA8-EC4491DCAFED@.microsoft.com...
> Does anyone know of anyway to read the transaction logs? The reason why I
> am
> curios is, the transaction logs are way to large for the amount of
> transactions we are running(yes, the transaction logs are set to
> automatically grow). Our application would not send that amount of
> transactions to the database. The other thing I am thinking is that there
> is
> another db within this sqlserver that I think access this DB and I think
> the
> transaction logs would prove this.
> Thanks for your assistance in advance....
|||TJ
Another option to consider is the Bulk-Logged recovery mode. Bulk-logged
has better performance than Full with large bulk inserts and bcp operations
because the transaction log files should not grow as quickly as a result of
only recording complete transactions. In other words, you sacrifice the
ability to recover row by row that might occur with large batches.
Regards,
Keith
This posting is provided "as is" without inferring rights or warranties.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eOihJpswFHA.2076@.TK2MSFTNGP14.phx.gbl...
> What recovery mode are you in? If it is FULL and you don't issue regular
> Log backups it will continue to grow and grow. Change it to simple mode
> and you should not see it grow any more. If you really want to see what
> is happening on the server you should use Profiler or Trace.
> --
> Andrew J. Kelly SQL MVP
>
> "TJ" <TJ@.discussions.microsoft.com> wrote in message
> news:92CF3A8E-4DA0-4E1B-BCA8-EC4491DCAFED@.microsoft.com...
>