Take a look in the stairways section, for the stairway to integration services also there is plenty on the internet if you use a defined search term like using ssis...

create a data flow task

drag in a ole-db ado.net source connector, up to you which

drag in an excel destination connector

create the connection strings in both of the connectors to the...

If something can be done in SQL do it in SQL not CLR is my mantra.

String splitting can be done in either format, just depends on the load your putting...

Yes, that is correct, if the db is sized at 100GB but only has 50GB used then the backup would be around 50GB (give or take), same again, if the...

Gangnam Style

Run a repair on the installation, which should re-register the dll's etc and get intellisence working again.

If you drop tables or move data from the main database to an archive database then you are effectively creating white space.

While white space is backed up in the backups...

What I believe you are looking for is a CASE statement

CASE WHEN R.FLDPHYSICAL = '110' THEN R.FLDDATEDUE ELSE '' END AS TB,

CASE WHEN R.FLDPHYSICAL = 'TBSS' THEN R.FLDDATEDUE ELSE ''...

Why do you need this to be in a CLR function?

There is a very good T-SQL function which you can find in my signature post by Jeff, but for ease...

Appreciate that you may have already checked this, but is it connecting to Exchange? If so have all the virtual IP's of the cluster been granted connect and send...

in theory yea but you will need to check the data yourself, otherwise your looking likely that the table is compressed

Sounds like you need to create the user based on the login then assign the nessesary roles to the user

Add something like the below to your script

CREATE USER [Domain\GroupName] FOR...

compression, sparse columns, different columns have data populated (e.g 9 out of 10 columns are null in archive, but 0 out of 10 columns are null in the main table)

whats in the SQL logs around the same times?

Check the windows logs, check the SQL server logs, they should contain the information about who/what/where/why/when restarted the SQL service.