Iron Speed Technical Forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment   Page 1 of 2      1   2   Next
supanes

Registered:
Posts: 111
Reply with quote  #1 
I have performance issues with my project, my database has 1,500 tables, but im only using 3 main tables and 10 for reference (foreigns).

I the 9.2 version, ironspeed only creates xmls for the used tables, now in 10 version, creates for all the objets in the database. I think this is a bug.

Is there a parameter to config this? i cant add new pages, rebuild my app or refresh eschema because take me 3 or 4 hrs to ironspeed responds...

my data access layer directory is 80mb in version 10 and 5 mb in 9.2

thanks for your help, i cant go on with my project and my deadline is very close
dingjing

Avatar / Picture

MVP Developer
Registered:
Posts: 256
Reply with quote  #2 
I usually wait until x.01 to upgrade.
akeshgupta

Avatar / Picture

Iron Speed MVP
Design, Develop & Deliver

Registered:
Posts: 1,095
Reply with quote  #3 
I made an application for database with 30 tables and I only selected 10 tables.  In my case, Iron Speed 10 did not make Data Access layer for all tables.  I am not sure what happened.  Is it possible that you selected all tables by accident once and then deleted all folders?  

Just wanted to provide my feedback.  I am using SQL 2012 DB with Visual Studio 2012.

__________________
Akesh Gupta
Light Speed Solutions, LLC.
If I rest, I will rust !   Let's share the knowledge !
trice160

Registered:
Posts: 12
Reply with quote  #4 
If you click on the database tab, you can exclude tables from the application.

To do this, click on the table you wish and then change this property:

Property

Description

Include table in application

Indicates whether the supporting database access code should be created for the table.  Database tables and views used by the application automatically have this option selected.  However, you may instruct Iron Speed Designer to include code for tables not directly used by the application’s web pages.  This is useful in circumstances where a non-web interface is being used, such as a web service or a Windows application.


I think you should be able to do the same thing for Views and Stored Procedures.

Tim

__________________
Tim Rice
TKR Associates, LLC
janthony

Registered:
Posts: 139
Reply with quote  #5 
Supanes,

A change with v10 is that it appears to create the ISD XML file in the Data Access Layer folder for all tables and views in the database. Even though it does not build them into the Data Access Layer until you intentionally include them in the application, put them on a form or have a foreign key set to them.

Is there only the XML files, or is it building the Data Access Layer for each table also?

Thanks,

Jim


 
akeshgupta

Avatar / Picture

Iron Speed MVP
Design, Develop & Deliver

Registered:
Posts: 1,095
Reply with quote  #6 
Jim:

Your observation is correct.  It does create XML files for every table.  I am not sure about its reason but it does not create business layer and data access layer classes for those tables which are not included.

These XML files are not needed for the production run, so in case they are taking too much space, you can exclude them from the production copy.

HTH,

__________________
Akesh Gupta
Light Speed Solutions, LLC.
If I rest, I will rust !   Let's share the knowledge !
supanes

Registered:
Posts: 111
Reply with quote  #7 
for tables that i dont use, only create xml files. Akeshgupta is right. My problem is that ironspeed take hours to rebuild, or add a new page, because in my database are 1,500 tables...  so everytime i add a new page, take 4 hrs to complete the process. 

i only use 3 tables and have 10 references...

is there any problem if i delete manually the xmls files? 

im sure i dont add all the tables to my project, i work one by one.


Quote:
Originally Posted by janthony
Supanes,

A change with v10 is that it appears to create the ISD XML file in the Data Access Layer folder for all tables and views in the database. Even though it does not build them into the Data Access Layer until you intentionally include them in the application, put them on a form or have a foreign key set to them.

Is there only the XML files, or is it building the Data Access Layer for each table also?

Thanks,

Jim


 
Kirill

Avatar / Picture

Registered:
Posts: 223
Reply with quote  #8 
In version 10 Designer creates xml files for all tables, not data access layer though. That is done for several reasons, mainly to allow toolbox population for objects not included into current schema and speed up Application Wizard by not scanning schema again and again.
Generally xml files do not hurt anything but it seems in this case something is going wrong.
So I suggest to open support case and upload your schema (do not need data or application, you may just mention which tables you are using so we can test). We would run profiler to identify the problem.
supanes

Registered:
Posts: 111
Reply with quote  #9 
my support case was open yesterday (36600). today i sent my db schema. So im waiting right now.

Thanks for your support
Kirill

Avatar / Picture

Registered:
Posts: 223
Reply with quote  #10 
Yes, I see it. We are working on it.
srandrx

Registered:
Posts: 28
Reply with quote  #11 
I believe this is a related issue ..... 

1)
Application Wizard generates duplicates pages of each type for every table selected.
(see attached)

2)
Application Wizard generates QuickSelector.aspx pages for each table (these were not selected in the Wizard) that has a foreign key pointing to the selected tables. I can understanding that tables with are pointed to by a foreign key will have QuickSelector.aspx pages generated but not the other way around as is happening.

Support case has been sent:36617 

Attached Images
Click image for larger version - Name: duplicates.png, Views: 18, Size: 25.02 KB 

__________________
- (S)(R)and(R)(X)

supanes

Registered:
Posts: 111
Reply with quote  #12 
you are right.. i hope they find all the reasons and fixit soon... for our feedback, i delete all the xmls files that i dont use ... that was the only way i can work in my project... 


srandrx

Registered:
Posts: 28
Reply with quote  #13 
Quote:
Originally Posted by srandrx
I believe this is a related issue ..... 

1)
Application Wizard generates duplicates pages of each type for every table selected.
(see attached)

2)
Application Wizard generates QuickSelector.aspx pages for each table (these were not selected in the Wizard) that has a foreign key pointing to the selected tables. I can understanding that tables with are pointed to by a foreign key will have QuickSelector.aspx pages generated but not the other way around as is happening.

Support case has been sent:36617 


I am attaching another image to clarify point 2)


Attached Images
Click image for larger version - Name: QuickSelector.png, Views: 18, Size: 55.89 KB 

__________________
- (S)(R)and(R)(X)

Kirill

Avatar / Picture

Registered:
Posts: 223
Reply with quote  #14 
Yes, Quick Selector will be generated for all tables in use, i.e. all table that have business layer generated. That is necessary to generate foreign key controls.
Application Wizard does not generate duplicates UNLESS you select same pages for the same table again.
srandrx

Registered:
Posts: 28
Reply with quote  #15 
Quote:
Originally Posted by Kirill
Yes, Quick Selector will be generated for all tables in use, i.e. all table that have business layer generated. That is necessary to generate foreign key controls.
Application Wizard does not generate duplicates UNLESS you select same pages for the same table again.


You are quite right Kirill about the generation of duplicate pages.
The example I sent seems to be a one off situation :-
it was a brand new application, pages generated were put in a single folder. That folder was deleted and pages then selected to be generated in folders based on Table name.

However I am unable to replicate the problem by recreating the steps described above.
I also tested various other permutations and all now yield consistent correct results.

Hence I would consider the duplicate page generation a closed case.



__________________
- (S)(R)and(R)(X)
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.

Download Iron Speed Designer

Terms of Service Privacy Statement