check out Shrink database in Books Online !

(or shrink file if you only want to do a single file)

Be aware that this will interfere with ongoing operations !

If this is the first alert on this sqlserver, you may have to stop/start sqlagent.

try this:

RAISERROR (17890, 10, 1) with log

we cycle the errorlog every sunday using a sqlagent job.

If you want to cycle, based on the file size, you'll have to write your own proc.

e.g. this one monitors sqlagent.out...

Nice feedback all.

Even the ( drum roll ) worked :w00t:

I didn't realize you actually wanted to consult it with EM. Sorry for that:blush:

With EM Management, SQLServer errorlogs then right click and check that setting.

As you've found out, you really need the original size to restore a database.

With db sizes growing, and your db still being small but expected to grow fast, maybe now...

Well... I guess it is undocumented (in bol), so use carefully.

You could use master..xp_readerrorlog

I haven't got all info at hand, but if you search the net, you'll find it for...

? Edition and version of your sqlserver please.

- chances of locking or deadlocking ?

- online or offline rebuild ?

That's one of the reasons we always urge people to put a clustering index on every table !

( unless it is proven to really hurt performance 😉 )

It's a...

Here's another post handling this issue...

http://www.sqlservercentral.com/Forums/FindPost570917.aspx

just open the script with SSMS in a query window.

One of your SSMS tabs is named "Query" there is an item named "SQLCMD mode".

you're suffering another bad practice .....

and you'll have to pay the price to get rid of it.

Don't mess with system objects !

That's like: I'm sysadmin of the dbserver hosting...

bulk recovery only doesn't log bulk operations (see BOL ! )

So classic update statements are still written in full to the log !!

If you log did grow to big, you...

is it your dbmail failing (error info ?)

or is it your mailserver holding back the mails because of some anti spam measures ?

Check with your mail admins.

problem solved.

SELECT TOP 1 *

INTO #sysobjects

FROM [dbo].[sysobjects]

where 0 = 1;

ALTER TABLE #sysobjects ADD [schemaname] [VARCHAR] (48) NULL ;

-- DELETE FROM...