The " xx" in the "20 xx" above changes based on what version of the documentation you are looking at, but starting with SQL Server 2008, that xx will be: "08", "12", or "16". All user-created databases in SQL Server 20 xx are always enabled for full-text indexing. sp_fulltext_database does not disable the Full-Text Engine for a given database. Has no effect on full-text catalogs in SQL Server 2008 and later versions and is supported for backward compatibility only. Looking at the MSDN documentation for sp_fulltext_database we see the following note: Going to Sql Server Management Studio and right-clicking on the server > properties > advanced > parallelism I found some configurations, but they do not seem to affect this automatic definition of 5 seconds. This command does not exists in my publishing script, so I assume that an internal command or configuration is doing it. Using the SqlServer profiler during a deploy I found out that something is changing the lock timeout to 5 seconds. My question is: Is this the only way to solve the problem? Changing the LOCK_TIMEOUT? Since the publishing process is done by a auto-generated script, I do not think it is a good idea to change the script manually. Trying to change the lock timeout limit to 20 seconds through the query: Searching for further explanations, I found out that the default lock timeout limit is -1, which is unlimited. It happens when two or more publishing scripts are being executed in parallel, more specifically on the procedure sp_fulltext_database. Sometimes, during this publishing process we got an error: " Lock request time out period exceeded". sqlproj file executed by MSBuild, which generates a publishing script. There I need to publish many SqlServer databases simultaneously on the same instance. I am working on a continuous integration environment using SqlServer2014.
0 kommentar(er)
