Articles Tagged 'sql'

You’ve probably encountered cases where it looks like you need another SELECT statement inside your main statement.
Is it possible to use nested SELECTs in ESQL? 
Yes, it’s possible!
In this article, we’ll explain the nested query (SELECT) and how to use it efficiently.

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.

You may want to extract all the artifacts that have a specific person is assigned across all products, to see their current work. 
This article provides an example of such a report.

A customer once asked how to create a velocity comparison chart for their Scrum Team to measure planned versus actual velocity across the releases. This article addresses how this chart can be created.

A customer recently asked about creating a custom graph based on a set of values in a custom list on an artifact. This article explains how this can be done. 

A customer once asked how to create a list of all test cases that have electronic signature approval recorded.  For example, let us say that you have electronic signature turned on for a specific transition operation in the Test Case. Then, how do we create a list of all the test cases that have electronic signature recorded? 

When you upgrade from v5.4 to v6.0, unlike previous versions of the upgrader, we don't delete the entire database and recreate it. The upgrader makes the changes to live database in-situ. However if you have missing foreign key constraints in the v5.4 database it can lead to bad data that breaks the installer.

Sometimes when you are running Rapise tests you need to run direct database queries to prepare the data in the test application, or you need to make queries against the database to verify that some user interactions left the data in a specific state.

The sample script below illustrates how you can call database queries directly from the Rapise scripting editor:

If you need to connect Database object to PostgreSQL database follow these simple steps.

If you need to connect Database object to MySQL database follow these simple steps.

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.

Sometimes when running the Spira v6.0 installer to upgrade from v5.4.0.4 to v6.0 you get the following error:

Table or indexed view 'TST_ATTACHMENT' does not have a full-text index or user does not have permission to perform this action.

This article describes the cause and provides the solution

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.

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 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.

Our Spira platform (SpiraPlan, SpiraTest, SpiraTeam) has powerful custom reporting capabilities that let you build custom reports using the Microsoft Entity SQL language. This article provides some pointers on writing such reports.

Sometimes you want to create a new custom report with a list of fields from SpiraTest that includes the date that a test cases was executed or the date that a defect was logged, but you don't want to clutter the report with the time part. Alternatively you want to join two tables on a date-time field where only a date comparison is needed.

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.