|MS SQL Server setup||Lind-Thomsen||2015-09-24 01:43|
I'm still having problems with getting a running Labkey installation using MS SQL Server.
The basic questions are:
1: What is the preferred process to install a Labkey server using MS SQL Server when you don't have full permission/control of the server and want to be certain that the labkey admin have all the necessary permissions (at the moment the labkay admin is owner of the database) ?
2: Can you describe what permissions are needed (besides from being owner of the database) in the database to successfully run labkey?
3: Must it be the labkey server that runs sp_updatestats or is it OK if we have the option 'Auto update statistics' enabled on the database?
environment: MS SQL Server 2012, tomcat 7,windows 8 server. Manual install of Labkey
I'm not sysadmin so I don't have full control over the database, I have to ask our central IT department to do stuff, which takes 1-3 days depending on how busy they are.
There are (at least) two issues:
Needs to be part of core schema, but the core schema cannot be made before the initial run of the server.
I get an error if I try to create the core schema in advance and assign the GROUP_CONCAT functions to it before I start the server ("core schema already defined" exception). After moving GROUP_CONCAT back to dbo and remove the schema. I get another error "DROP ASSEMBLY failed because 'GroupConcat' is referenced by object 'GROUP_CONCAT_D'" but I was able to start labkey. Then it seemed to work but when I installed a module I was back to a previouos discussed "FastaAdmin already exist" exception.
Need permission to run this stored procedure(in our system we don't have this pr default), this must be assigned before creating any database objects. Is it important who runs this procedure, as long as it is run?
Will the following process work (using the labkey admin user):
1: create the database
2: Set permission to run sp_updatestats
3: start Labkey server and finish the basic installation process.
4: install GROUP_CONCAT
5: Move GROUP_CONCAT to core schema
6: Restart server
Appreciate any comments and suggestions.