What is your reasoning behind wanting to shrink the database?

The approach I would take it to leave it as is and do not shrink unless there is a valid business...

Something like the following will do the trick

DECLARE @sql NVARCHAR(MAX)

SELECT @sql = REPLACE(

CAST(

(

SELECT 'USE ' + QUOTENAME(name) +';' + CHAR(13) + CHAR(10) +

'SELECT * FROM INFORMATION_SCHEMA.COLUMNS' + CHAR(13) + CHAR(10)

FROM...

OS Error 5 is access denied, ensure that the account running SQL has the nessesary permission to the directory

Is the Oracle driver you installed a 32 bit driver or a 64 bit driver?

Better scenario is do not shrink the database at all, it causes a whole heap of potential problems and fixing them will only make the database bigger again, so you...

Seems like an error with the dot net framework, I would suggest re-installing

Restore database.

I never trust the GUI to do exactly what it says it is going to do, I prefer to do things in script, which is why that script button...

I just did a restore via the GUI and it did pick up the STOPAT date time I supplied. Strange that its not doing it on your side.

Yes on fail over if they are running as jobs then yes they will run as intended.

If you fail over and want to upload a new SSIS package you will...

There is the problem, the last log restore should specify the STOPAT clause detailing SQL where to stop restoring the log, you can manually add it in at the end...

Please look through the Windows logs for the reason why the SQL service errored while starting and post the results.

Run through the restore again in managment studio but instead of hitting run, hit the button at the top and script it to a new query window and post the...

What was the command that you used to restore to the point in time?

No, you can use the command line based tool instead to upload the package if you dont want to do it via SSMS, that way you wont need the SSIS...

You need to ensure that the account running the SQL server service has access to write to the unc path