The issue with this approach is that the user is free to enter anything - a date in a format other than dd.mm.yy, or even any other random string into the Date column. They will be able to successfully enter it, but when you query it, the query will fail. This is the perennial problem with storing dates and times as character strings.
If you can ensure that the data in the Date column will always conform to the dd.mm.yy format, then you should be able to succesfully create a computed column and use it. The formula for the computed column can be simpler as shown below:CREATE TABLE #tmp
(
[Date] NVARCHAR(50),
[time] TIME,
DateAndTime AS CONVERT(DATETIME,[Date],4) +[time]
)
-- this should work correctly.
INSERT INTO #tmp VALUES ('15.02.12','18:07:33.0000000')
SELECT * FROM #tmp;
-- this insert will succeed
INSERT INTO #tmp VALUES ('blabla','18:07:33.0000000');
-- but the select will fail.
SELECT * FROM #tmp;
DROP TABLE #tmp;