Highlighted
Regular Contributor.. Regular Contributor..
Regular Contributor..
1336 views

Concepts about the database creation in LoadRunner and imported to SQL Server

Hello everyone! 

I hope you are doing well.

I have many questions about different concepts of LoadRunner Analysis with SQL Server. I use LoadRunner 12.50, SQL Server 2008R2 Express and  Windows7 x64. In the atached file (images.zip) you can find the images I will name along the message.

Today I have been working for having a database of one of the results collected from one test we launched “imported” into my SQL SERVER 2008 Express R2 software. Which is the last version of SQL Server that can I install and LoadRunner Analysis supports?

So, first of all I have installed SQL SERVER 2008 Express R2. Once it has been installed, I have edit the analysis Database options like in the picture named 01_Analysis_Database_Configuration

In this step I have the error of the pictures 02_1_Warning_Test_Parameters and 02_2_Warning_Test_Parameters

What I have to do to resolve this warning?

Although this problem, I have continued, and when I save a LoadRunner Analysis session it appears a new database which are named like this: res_5626967DB and res_7437309DB. Why are named like that? Can I change them?  Look the 03_Database_Names.png file

Another thing that I have found are many tables named like this: TxxxxxxxT. How can I know what data appear in those tables? And why are named like this? 04_Table_Names.png

Why the diagram folder is empty? How can I do or where can I find a relationship diagram between the tables? 05_Relationships_Diagram.png

And finally; why Dbo.MastersMap table is empty? I have read that in this table there is a column (sql) which, more or less, shows the relationships between tables.  06_MastersMap_Empty.png

If you don’t understand something please let me know.

Thank you very much for your time.

Best regards

0 Likes
3 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Concepts about the database creation in LoadRunner and imported to SQL Server

  • 2008 R2 is supported one with LR12.50
  • The warning is becuase you are using same machine as LR & SQLS and same path.
  • For other queries, the structure of the Analysis session database is not officially published to customers. You may use Analysis API for such things which allows almost any info available in analysis session.

 

 

 

0 Likes
Highlighted
Regular Contributor.. Regular Contributor..
Regular Contributor..

Re: Concepts about the database creation in LoadRunner and imported to SQL Server

Thank you very much for anwsering.

I have understand everyghing you say, but it doesn't resolve my problem.

Supose that I execute the same test along a week for five times, and I want to report showing the evolution of the response time of the third transaction of the first script or the bandwith consume comparation between the first and the third test.

If I have an organized database the time I will spent for doing that report may be less than if I have to see one by one every test results.

What can I use for resolve this problem?

Thank you for your time.

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Re: Concepts about the database creation in LoadRunner and imported to SQL Server

Why don't you try usiing the LoadRunner Analysis 's "Cross Results" option?

The Cross Result dialog box enables you to compare the results of multiple load test scenario runs. For detials visit : http://lrhelp.saas.hp.com/en/latest/help/WebHelp/Content/Analysis/104350_t_generate_xresult_graphs.htm

 

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.