Triggers need to be able to handle any given number of rows.   You can not rely on there always being just 1 row getting inserted.   Any multi-row insert will result...

Your question has inadequate detail.   You can certainly run SQL 2012 on that hardware, but the only really important question is what kind of workload you expect to get out...

There is no reason to use anything more than a BIT column to record the vote value.   1 = FOR, 0 = AGAINST, NULL = ABSTAIN.   Then add a 2nd...

1.)  You have to have network connectivity between the SQL Server and the Linux Server, or nothing you do will work.   No network connectivity and you are simply going to...

Let's try this:
CREATE TABLE #MyTable (
    Employee VARCHAR(1) NOT NULL,
    [Period] VARCHAR(7) NOT NULL,
    personalid VARCHAR(7) NOT NULL,
    Product VARCHAR(5) NOT NULL
);
INSERT INTO #MyTable (Employee, [Period], personalid,...

And this will be a  much better performing scenario due to the clustered indexes:
CREATE TABLE #TriggerDate (
    MyAccount int,
    MyDate date,
    UNIQUE CLUSTERED
        (
        MyAccount ASC,
        MyDate ASC
        )

Here you go...
CREATE TABLE #TriggerDate (
    MyAccount int,
    MyDate date
);
INSERT INTO #TriggerDate (MyAccount, MyDate)
SELECT 1, '2018-07-28' UNION ALL
SELECT 1, '2018-08-02' UNION ALL
SELECT 2, '2018-08-03' UNION ALL
SELECT 3, '2018-07-31';

CREATE TABLE #History (
    MyAccount int,
    DateSold...