What have you tried so far? What are the errors you encountered?

I think if you add a "Execute Process Task" to your package, you should be able to get it....

But remember: the LOG backups are primarily for recovering lost data. It is not intended to do auditing. There are other features and tools to do auditing.

I don't have any experience with their tool, I just googled a bit...

There is too little information. Like I...

Contact Microsoft and ask for it 😛

http://support.microsoft.com/contactus/?ws=support&SegNo=1#livehelp_contact

It depends... It al boils down to good capacity planning and disksize monitoring.

Aks the business/developers for the expected growth of the database. Set the initial size to the expected size...

To shorten the cut-over time, you should create full backups (at least of the greater databases) and restore these on the new instance with norecovery. If you do this the...

Thank for pointing that out. I was so focused on...

Does this statement work?

CREATE VIEW v_WhatsUp_Assyst

AS

SELECT nDeviceID

, nDefaultNetworkInterfaceID

, item_id

, item_keya COLLATE Latin1_General_CI_AS as 'item_keya'

, nDeviceGroupID

, sGroupName COLLATE Latin1_General_CI_AS as 'sGroupName'

, nDefaultNetworkInterfaceID

, sNetworkName COLLATE Latin1_General_CI_AS as 'sNetworkName'

FROM WhatsUp_Assyst_replicatie.dbo.device

, WhatsUp_Assyst_replicatie.dbo.item

, WhatsUp_Assyst_replicatie.dbo.DeviceGroup

, WhatsUp_Assyst_replicatie.dbo.NetworkInterface

UNION...

SQL Surfer '66 (8/15/2013)

---

Instead of clicking OK to start the back up, click in the Script button on the top. This generates a script in a new query windows...

Sorry, I was too much copying...

Remove the COLLATE commands from all ID fields. Only leave the COLLATE commands on the VARCHAR fields.

Make sure that all SQL related services are stopped. This also includes the SQL Browser and possibly a third party backup application. Also make sure that no applications connect to...

Make sure the job_id in the select correspondents with the job_name in the start command. That's a mistake I have made in the past 😉

CREATE VIEW v_WhatsUp_Assyst

AS

SELECT nDeviceID COLLATE Latin1_General_CI_AS

, nDefaultNetworkInterfaceID COLLATE Latin1_General_CI_AS

, item_id COLLATE Latin1_General_CI_AS

, item_keya COLLATE Latin1_General_CI_AS

, nDeviceGroupID COLLATE Latin1_General_CI_AS

, sGroupName COLLATE Latin1_General_CI_AS

, nDefaultNetworkInterfaceID COLLATE Latin1_General_CI_AS

, sNetworkName COLLATE Latin1_General_CI_AS

FROM WhatsUp_Assyst_replicatie.dbo.device

, WhatsUp_Assyst_replicatie.dbo.item

, WhatsUp_Assyst_replicatie.dbo.DeviceGroup

,...

After you noticed that the database couldn't come online and it was due to a mistype, you could just execute another ALTER DATABASE command with the correct filepath. That would...