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...

or .... if you're allowed to do so during your update ... put your db in simple logging ...

Keep in mind..... backup before, symple recovery, your stuff in batches, full...

if sqlagent is not activated you may not see sqlagent stuff.

you can use sp_configure to still have all sqlagent stuff visible.

-- enable Agent XPs

EXEC sp_configure 'Agent XPs','1'

RECONFIGURE

GO

You may need restart sqlagent to activate the first alert !

for the rest: It does not know a individual address from a group address

nailosuper (10/23/2008)

---

Yes i looked. I didn't find something so different. Here's what i saw :

BackupMedium::ReportIoError: write failure on backup device '\\XX.bak'. Operating system error 1130(error not found).

any ideas ?...

Keep in mind that the "-i" file needs to be available at the server or client where you actually launch the SQLCMD (or osql) !!

edit

this also goes for the -o...