Guillaume.G
26th September 2002, 18:42
What is the solution for separate the data & index in the SQL server 7.0 ??
And in the second phase : is it possible to separate the different companies in several files ? (like Oracle with the Ora_storage)
Thank You
Guillaume G.
tsnaresh
27th September 2002, 00:29
For SQL 7.0 baan has mssql_storage file under /lib/mssql.
Where you can specify different segments (file groups) for indices and tables. Also different companies can be created on different file groups.
The mssql_storage file looks as follows:
*:650:T:group:011:5:SEGMENT SEG650T
*:650:I:group:011:5:SEGMENT SEG650I
In the above example company 650 tables will be created on SEG650T group and Indices on SEG650I.
NOTE: These definitions need to be present prior to creation of tables. Hope this helps.
Guillaume.G
27th September 2002, 15:45
Hi,
Thank you, but i'm another questions :
In documentation (U7042B - MS SQL Server Database driver internal in appendix D p7-3) at the storage parameter segment is only available for SQL6.5 and not for SQL7.0.
is it right or not ???
And i'm a newbie in SQL7.0. What is a segment in SQL server (how defines this ????? :confused: )
Thank your for your help
Guillaume G
tsnaresh
30th September 2002, 23:17
When you create a database in SQL server by default it creates on Primary segment (or file group). You can create secondary file groups as follows:
Using EM(Enterprise Maanger) connect to SQL server, expand databases, select baan database and go to "database Properties", under general Tab insert new database file name. location, space allocated and in the last field is file group (this is the segment name in the mssql_storage file).
Once you finish, click apply. You are done. Use the same file group name in the mssql_storage file.
Hope this helps! Good Luck!!!
tsnaresh
23rd October 2002, 20:04
I was creating a new company last weekend and wanted on separate file group. to my surpirise inspite of specifying the new file group in the storage the tables were created on the primary segment. I don't know why I was able to do last time, it could be it was possible with earlier porting set. Any way to over come this problem, I did the following:
1. I have changed the default file group from PRIMARY to new file Group. It can be done as follows:
alter database baandb
modify filegroup newgroup default
2. Create tables in this new company using session create tables in baan (ttaad4230m000).
3. The tables should now be created on the new file group, you can check with sp_help <table name>, the output shows data located on new file group.
4. Change back the default file group to PRIMARY as follows:
alter database baandb
modify filegroup [PRIMARY] default
You might have already figuredout this but just thought this work round might help others.
cheers!
tsnaresh