VERIFIED SOLUTION i

Resolve SQL database install script warning messages in EngageOne Server v4.4

Product Feature: Installation / Upgrade
 

Issue

When executing the SQL database script "EngageOne-mssql-db-install.sql", the following two groups of warning messages are encountered:

SETUSER permission denied in database 'eos'.
Warning: User types created via sp_addtype are contained in dbo schema. The @owner parameter if specified is ignored.

and

The module 'usp_p_doc_logical_path' depends on the missing object 'usp_p_doc_logical_path_one'. The module will still be created; however, it cannot run successfully until the object exists.
The module 'usp_s_check_show_share_folder' depends on the missing object 'usp_s_doc_check_acl'. The module will still be created; however, it cannot run successfully until the object exists.
 

Cause

The warning messages occur following the database script execution during the installation of EngageOne Server.

Resolution

UPDATED: November 23, 2017
The warning messages can be ignored and it should not affect the EngageOne installation.

For additional verification, for the first group check to ensure all the user data types have been successfully created by executing the following query:
select * from sys.types where is_user_defined = 1;
This should return 21 rows, containing definition of all the user data types created during the script execution.

The second group is the consequence of the order in which stored procedures are created in the database.
There are two cases where the order isn’t right, as the stored procedure used inside another stored procedure is created after the one which calls it, resulting in a warning message.

To verify all the stored procedures stated in the messages exist,  execute the query below:
select * from sys.procedures where name in ('usp_p_doc_logical_path', 'usp_p_doc_logical_path_one', 'usp_s_check_show_share_folder', 'usp_s_doc_check_acl');
This should return 4 rows.