The database should be attached back as long as you properly shut down the services. Can you post statement/commands here to show how did you try to get the database...

Generally, SQL Server errorlog files are quite small in term of size. Why they want to do this?

You could set quota to log folder to SQL Server service account.

The UNC path should be \\server\drive$\directory\filename.BAK. Make sure SQL Server services account are able to write to it.

You can't use the built in log shipping wizard to do that in SQL Server but you can create your own log shipping solution to constantly copy database and log...

Another work around.

declare @foreignkey sysname

declare @referencingtable sysname

declare @cmd sysname

DECLARE fkey_cursor CURSOR FOR SELECT object_name(constid), object_name(fkeyid) from sysreferences

OPEN fkey_cursor

FETCH NEXT FROM fkey_cursor INTO @foreignkey, @referencingtable

WHILE @@FETCH_STATUS = 0

BEGIN

select...

Database size = MDF files size + LDF files size.

Reserved = data + index_size + unused

MDF files size = reserved + unallocated space

SELECT sf.groupid AS GroupID, substring(sf.groupname,1,30) AS FilegroupName,

substring(so.name,1,30) AS ObjectName

FROM sysobjects so

INNER JOIN sysindexes si ON so.id = si.id

INNER JOIN sysfilegroups sf ON si.groupid = sf.groupid

WHERE si.indid = 0 and...

The processes that extract data from production database, transform and load them into your DW depend on your business requirements.

See "Extracting Data from Operational Systems", "Cleansing and Transforming Data",...

See "Autocommit Transactions", "Implicit Transactions" and "SET IMPLICIT_TRANSACTIONS" for explaination and examples in BOL

quote:

---

6. Specify the Transaction Log Share - Here, I put the share I created on the standby server with UNC \\machine\MSSQL\LogShipping\Test