Adam

You could create a job that writes a row to a table and runs whenever the text "Database backed up: Database MyDB" appears in the error log.

John

Arthur

Create a job to do the alerting (send a mail, FTP a file to your desktop, whatever) and, instead of scheduling it to run at a certain time, have it...

I take it you're referring to the TCP port on which SQL Server listens?  This information is stored in the registry, so you can use the reg add utility to...

Paul

I would stick with RAID1, even if you have logs from more than one database/instance on it.  The reason is that RAID5 is good for reads, but is slower for...

AJ

It sounds like your network is busy or unreliable and therefore your backup cannot complete.  Is the database that is failing the biggest, by any chance?  Or is it being...

SELECT o.name, s.groupname

FROM dbo.sysfilegroups s

JOIN dbo.sysindexes i

ON i.groupid = s.groupid

JOIN dbo.sysobjects o

ON i.id = object_id(o.name)

AND i.indid in (0, 1)

Claudia

It's not necessarily a bad thing for the log to be bigger than the data - especially if you have a high volume of transactions.  What you need to do...

Ahhh - snapshot replication.  While the snapshot is being applied, every insert will be written in the transaction log.  That's why it keeps growing.

I think you're confusing the transaction log...

Alex

In that case, you can write some VB in another Excel workbook that saves your file as an xls and creates the name, then schedule that from SQL Server or...

Michael

Check out the topic Identifying a Data Source Using a Linked Server Name in Books Online.

John

Alex

Will this work for you?

(1) Save your spreadsheet as an xls file.

(2) Create a named range in the spreadhseet to cover all the data.

(3) In Enterprise Manager, create a Linked...

Cláudia

This is normal behaviour.  Your destination database is having inserts, deletes and/or updates done on it and these operations will be recorded in the transaction log, causing it eventually to...

Something that you touched upon is not having control over the membership of the Windows group.  If you grant a Windows group access to your SQL server, bear in mind...

Luis

If your update query looks like this:

UPDATE MyTable

SET MyCol = 'NewValue'

WHERE SomeOtherColumn = 'SomeOtherValue'

Then you can see what rows you are affecting by running this:

SELECT * FROM MyTable

WHERE SomeOtherColumn =...

I'm liking it - even though it doesn't auto-complete information schema views.  Unfortunately I'm stuck with a Windows NT box for administering my production servers and so I can't use...