Or you can also specify the RETAINDAYS or EXPIREDATE parameters in the backup syntax, to let sql overwrite the backups or not.

I don't think you can do it with SQL replication, only with snapshot. Because Transactional replication will save the changes into the SQL Log file, and merge replication saves changes...

No, you can't. You must have a conecction. It can be a Dial up connection.

Unless you manually transfer the changes by CD, diskette or wathever.

Are the files taken by a running backup job?

Are you then copying the files to a tape drive?

The easiest way for me, but maybe not the best in performance could be to use a couple of cursors:

CREATE TABLE #1

(Name VARCHAR(20),

SAl INT)

GO

INSERT INTO #1 VALUES ('Tom', 20)

GO

INSERT INTO...

You can publish and subscribe in the the same server, but not in the same databases.

You can use that between two different databases...

That shouldn't happen. There must be a problem with the filter you specify.

Can you post the function you use to create the filter?

That is the error it shows when trying to attach?

Check the SQL log to see what it says before dettaching the db when it was in status suspected and please,...

Can you post the statement you used?

Be sure to specify the right domain.

Also with the values passed specify the 'N' letter before the value.

If you want to know when the db was last changed for example adding a new table you can query the creation date in sysobjects table...but if you mean the...

No unless you have that table in a separate file and separate filegroup, allowing you to backup a single file wich contains a single table.

You can also export the table...

This QOD is particular because as you can see in the other topic, the correct answer is wrong, because 'None of the above' is the right one.

But check answers 1...

For me the best way to filter is to save the output into a SQL table and then apply T-SQL commands to filter.

Also is better and faster to save first...

If possible run profiler and do the same you did when the Agent failed to know wich command could cause the error.

Do you have replication set up?

Log shipping?

MAster/Target Servers?