Not sure if this is the right forum, so I apologize in advance.
I want to put an index on certain columns of my database. I understand it needs to be done in Sybase and not in Servoy. I downloaded Sybase Central but it wants a username and password. Where would I get that? Is that something Servoy gives us or do I need to get in touch with Sybase? Also, the only database it shows is servoy_repository, not the other demo databases.
BillB:
I downloaded Sybase Central but it wants a username and password. Where would I get that?
By default this would be DBA / SQL.
Indeed Sybase Central is de easiest place to start. With some SQL commands, this also can be done from Servoy using the raw SQL plugin.
Thanks for the reply Marcel.
Yes I got the registration code for the sql anywhere 10. My confusion is this; I don’t want to install another database, I want to use the one that comes with Servoy, so why do I need to “install” SQL anywhere 10?
Also, do I need to go to the server anytime I need to create an index? Something doesn’t make sense here. I can administer Servoy Server with a browser, but to get at Sybase Central, I’d need a remote desktop connection. So do I use Sybase Central on the development computer and not the server?
Thanks Marc,
I tried the username DBA and the password of SQL but it says those are invalid. Maybe they changed from 9 to 10?
BillB:
Thanks for the reply Marcel.
Yes I got the registration code for the sql anywhere 10. My confusion is this; I don’t want to install another database, I want to use the one that comes with Servoy, so why do I need to “install” SQL anywhere 10?
Yes, that is how it is.
BillB:
Also, do I need to go to the server anytime I need to create an index? Something doesn’t make sense here. I can administer Servoy Server with a browser, but to get at Sybase Central, I’d need a remote desktop connection. So do I use Sybase Central on the development computer and not the server?
I think you make an error in your thinking pattern.
Servoy makes it clear, from the start, that it is separated from the datamodel. I agree, the fact that you can create a table etc. could be confusing but you could say that Servoy makes use of the data from a database but is not responsible for the design of the database…
Makes sense?
Marcel,
I understand that Servoy is only a front end. But when you can create a table, and you can create fields and other dataproviders, and importing the solution adds them to the database, it is not clear to me why I can’t add an index on that table when I create it.
The way I think it works is that an index is a separate table with the fields sorted in the order specified. Is that correct?
Anyway, I still don’t see why Servoy doesn’t give us a chance to create the index while we create the first table.
In any case, it is what it is. So if DBA and SQL are not the username/passwords, do I need to install the SQL 10 database? There is nothing about this in any of the 4 Servoy documents I’ve researched.
dba/sql are definitely the default username/password.
The version that you need to install depends on the version of Servoy (see one of the links in the first reply).
BillB:
Marcel,
I understand that Servoy is only a front end. But when you can create a table, and you can create fields and other dataproviders, and importing the solution adds them to the database, it is not clear to me why I can’t add an index on that table when I create it.
The way I think it works is that an index is a separate table with the fields sorted in the order specified. Is that correct?
No, it’s not correct.
Every Database has his own logic to implement indexing, his own type of indexes and his own SQL syntax to define them.
It’s not really up to Servoy to write a single GUI to create indexes for every supported database server.
Keep also in mind that if you deploy your solution to a medium-large company they will have their DB Admin and usually db admins are a bit jealous of their databases…
No problem, be careful when you create the indexes, sometimes indexes slow things down instead of speeding them up. Read the database documentation carefully, it’s really worth the hassle.