Articles Tagged 'sql server'

If you ever see the following message in the Application Event Logs on your SQL Server database server:
SQL Server has encountered X occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [Path to either your database's MDF or LDF files]
It can often mean that the Size/Shrink settings for the database files are not correct for the size of database. This articles suggestions some techniques for fixing this error message.

This article is obsolete.
The error was most common for SQL Server 2008/2008R2 editions and indicates SQL Server I/O Bottlenecks, as well as serious problems with your storage hardware you need to fix. These SQL Server editions are no longer supported.

Sometimes we get help desk tickets from on-premise customers regarding the performance of our web-based applications (SpiraTest, SpiraPlan, SpiraTeam and KronoDesk). Whilst every situation is different, this article provides some common best practices that should help having a high-performing system.

When using Spira or KronoDesk on a separate web and database server, the easiest configuration is to use SQL Server authentication to connect between the web server and database. However that means hard coding a password in the web server (in the Web.config file). So in this article we explain how to use Windows Integrated Authentication instead.

When using SpiraTest, SpiraPlan, SpiraTeam or KronoDesk with SQL Server 2012 or later, you may occasionally have a situation where the ID for an artifact (test cases, incident, ticket) suddenly jumps by exactly 1,000 values (e.g. from 214 to 1214 instead of just incrementing to 215).

During the course of investigating a technical support issue for SpiraTest, SpiraPlan, SpiraTeam or KronoDesk , the need may arise to run a query against your Microsoft SQL database. To do so, you will use Microsoft SQL Server Management Studio. If you did not install this when you installed SQL, you can install it from the original source.

When connecting from Spira or Krono installed on a separate application server to a remote SQL server, you may have difficulties connecting. This article describes the steps for making sure that your SQL Server can be accessed remotely.

This article answers some common questions about which databases you can run SpiraTest, SpiraPlan, SpiraTeam and KronoDesk on, and where you can get them from.

This usually just means that the restored database just needs to be linked to the existing database server login. This can be done by executing the appropriate SQL command listed below:

The SQL Server Database Engine Tuning Advisor examines how queries are processed in the databases you specify, and then recommends how you can improve query processing performance by modifying database structures such as indexes, indexed views, and partitioning. This can be used by on-premise customers to improve the performance of their Spira and KronoDesk instances.

When you are installing SpiraTest, SpiraTeam, SpiraPlan or KronoDesk on a database server with a large 'model' database sometimes the install will fail because the initial Spira/KronoDesk database is not large enough to contain your model database. This article provides the solution

This post shows you how you can migrate or downgrade a SQL Server database from one version to a lower or earlier one. E.g. 2016 to 2014, 2014 to 2012, 2012 to 2008 etc. This can be useful if you maintain a heterogeneous environment of SQL Server instances and you have a backup from a newer version that needs to be hosted onto an older version. This happens to us quite a bit when customers installed a trial on SQL Server Express (latest version) and we need to host it on one our cloud servers.

When you install SpiraTest, SpiraTeam, SpiraPlan, or KronoDesk on premise, you have a choice in different ways to configure SQL Server. Every situation is different, but this article presents some recommendations.

When installing Spira on SQL Server 2012 (any edition) using Windows Authentication, you may receive an error message "Cannot Create User" (or similar) during the installation. This is because of a configuration change in SQL Server 2012 (as opposed to earlier versions). This article explains the step needed to prepare SQL Server 2012 for installing Spira v3.x. Newer versions of Spira will not need this step as the installer has been updated.