The message means exactly what it says, SQL Server 2014 only supports the Tabular functionality in Enterprise or Business Intelligence edition:

https://docs.microsoft.com/en-us/sql/getting-started/features-supported-by-the-editions-of-sql-server-2014?view=sql-server-2014#BISemModel_tabular

Standard edition does support most of multi-dimensional functionality:

https://docs.microsoft.com/en-us/sql/getting-started/features-supported-by-the-editions-of-sql-server-2014?view=sql-server-2014#BISemModel_multi

So are you querying the database that is the target of the replication or the source of the replication?  I'm still not sure.  Also if you already have 2 copies...

I think your request raises more questions in me than answers:

1. What do you mean by DTS?  I sincerely hope you don't mean the old Data Transformation Services from SQL...

...Actually my task was to update  the data across different servers in different locations where the data will be same in all servers.  Any update\Delete\Insert in any table should...

Are Database1 and Database2 on the same server instance or are they separate?

The triggers could work if they are on the same server instance, but could be difficult to write...

You can use DBCC LOGINFO or sys.dm_db_log_info to determine which VLF's are available - as long as that database is not part of an AG.  The Status column will...

To figure out why your log file grew so much, you may be able to look at the default trace to see what caused the growths:

DECLARE @path...

Okay, so you do have some room here.  Do you know how much your files are growing by week or by month?

How much free space is on that D: drive as a whole, and are the data files also on the same drive?

With that much free space it should be able to shrink some after a transaction log backup.  Unfortunately I don't know a way to determine which VLF in the transaction...

Try this to see why it can't reuse the log space:

SELECT database_id, name, recovery_model_desc, log_reuse_wait_desc FROM sys.databases WHERE recovery_model_desc <> 'SIMPLE'

--edit oops I read your results wrong

• This reply was modified 4 years, 9 months ago by  Chris Harshman.

Check how much of...

And hopefully you are putting your backup files somewhere other than the server you are backing up correct?

What are the errors you receive with the large script?

Since this is a transaction log file, what Jeffrey says holds true, you don't need the TRUNCATE ONLY.

What I think is more important, before you try this, do you know...