SQL Server Table names and Stored Procedures

BLOMASKY

My system will have a lot of the "heavy lifting" done by Stored Procedures (SP).

I have a BO called "Item" the SQL Table in the testDB is named BASTESTDOMAINALC_ITEM Now, I can write my SPs to access this but when I go live, I will have to work with diff. table names. (I assume the "TEST" will no longer be part of the name.)

Is there a way for me to control the naming of the SQL tables so my SP will just have to be copied to the production database and I won't have to rewrite (and test!) all of them?

Thanks

Bruce

crisg0112

BLOMASKY wrote
My system will have a lot of the "heavy lifting" done by Stored Procedures (SP).

I have a BO called "Item" the SQL Table in the testDB is named BASTESTDOMAINALC_ITEM Now, I can write my SPs to access this but when I go live, I will have to work with diff. table names. (I assume the "TEST" will no longer be part of the name.)

Is there a way for me to control the naming of the SQL tables so my SP will just have to be copied to the production database and I won't have to rewrite (and test!) all of them?

Thanks

Bruce

Hi Bruce,

When you first create your business space, you have an option to 'allocate a different database' section. If you specify that, then all your 'tables' or Business objects (when deployed) won't have the BASDOMAIN_xxxxx format.

If you decide to use BASDB, then the format when deployed is DOMAINNAME_tablename; where domainname is your application name.

Hope it makes sense

BLOMASKY

You are right. It DOES!

However, the testing DB still has the extended name. Is there a way to have the testing DB use the same naming convention. Otherwise, I will still have to edit and test all of my SP when going from testing to production.

Thanks
Bruce

crisg0112

BLOMASKY wrote
You are right. It DOES!

However, the testing DB still has the extended name. Is there a way to have the testing DB use the same naming convention. Otherwise, I will still have to edit and test all of my SP when going from testing to production.

Thanks
Bruce

not sure how to do it on the testing DB.

on the help guide:
EXEC SP ‘proc1’ OF SQLServer WITH ‘@param1’=1,’@param2’=2 RETURN SomeObject
This stored procedure returns the specified records from an external database identified by the name SQLServer.

BenHayat

crisg0112 wrote
BLOMASKY wrote
My system will have a lot of the "heavy lifting" done by Stored Procedures (SP).

I have a BO called "Item" the SQL Table in the testDB is named BASTESTDOMAINALC_ITEM Now, I can write my SPs to access this but when I go live, I will have to work with diff. table names. (I assume the "TEST" will no longer be part of the name.)

Is there a way for me to control the naming of the SQL tables so my SP will just have to be copied to the production database and I won't have to rewrite (and test!) all of them?

Thanks

Bruce

Hi Bruce,

When you first create your business space, you have an option to 'allocate a different database' section. If you specify that, then all your 'tables' or Business objects (when deployed) won't have the BASDOMAIN_xxxxx format.

If you decide to use BASDB, then the format when deployed is DOMAINNAME_tablename; where domainname is your application name.

Hope it makes sense

Cris, I don't think that's true; Even if you allocate a different DB, your Test Tables will have the prefix, where as the live data won't;

Here is a customer table which gets "bastestdomaintxs_"
bastestdomaintxs_customer
In Test mode

BenHayat

BLOMASKY wrote
You are right. It DOES!

However, the testing DB still has the extended name. Is there a way to have the testing DB use the same naming convention. Otherwise, I will still have to edit and test all of my SP when going from testing to production.

Thanks
Bruce

Bruce, I've been struggling with the same issue (name wise). I have lots of data in test tables that I need to move to Live. when I export and import, it uses the testname which is not the same as live name.

If you find a way, let us know.

crisg0112

BenHayat wrote
crisg0112 wrote
BLOMASKY wrote
My system will have a lot of the "heavy lifting" done by Stored Procedures (SP).

I have a BO called "Item" the SQL Table in the testDB is named BASTESTDOMAINALC_ITEM Now, I can write my SPs to access this but when I go live, I will have to work with diff. table names. (I assume the "TEST" will no longer be part of the name.)

Is there a way for me to control the naming of the SQL tables so my SP will just have to be copied to the production database and I won't have to rewrite (and test!) all of them?

Thanks

Bruce

Hi Bruce,

When you first create your business space, you have an option to 'allocate a different database' section. If you specify that, then all your 'tables' or Business objects (when deployed) won't have the BASDOMAIN_xxxxx format.

If you decide to use BASDB, then the format when deployed is DOMAINNAME_tablename; where domainname is your application name.

Hope it makes sense

Cris, I don't think that's true; Even if you allocate a different DB, your Test Tables will have the prefix, where as the live data won't;

Here is a customer table which gets "bastestdomaintxs_"
bastestdomaintxs_customer
In Test mode

Hi Ben,

I did say when deployed 🙂

BenHayat

crisg0112 wrote
Hi Ben,

I did say when deployed 🙂

Hi Cris;
But his original question was, if there was a way that the table name would be the same in Test Mode and in Deployed mode.
He said "I have a BO called "Item" the SQL Table in the testDB is named BASTESTDOMAINALC_ITEM"
and he wanted to know if he could have the same table name (ALC_ITEM) in both Test and live Database.

crisg0112

BenHayat wrote
crisg0112 wrote
Hi Ben,

I did say when deployed 🙂

Hi Cris;
But his original question was, if there was a way that the table name would be the same in Test Mode and in Deployed mode.
He said "I have a BO called "Item" the SQL Table in the testDB is named BASTESTDOMAINALC_ITEM"
and he wanted to know if he could have the same table name (ALC_ITEM) in both Test and live Database.

You're right ! 🙂

BenHayat

crisg0112 wrote
You're right ! 🙂

Hope you didn't take it as I was challenging you. Just wanted to clarify! 🙂

BLOMASKY

Perhaps, the NEXT version will have an optional parameter in the BO for the SQL table name for both Production and Test Data...

Perhaps....

Maybe....

Bruce

crisg0112

BenHayat wrote
crisg0112 wrote
You're right ! 🙂

Hope you didn't take it as I was challenging you. Just wanted to clarify! 🙂

hey its all good mate !

kenlyle

+1 for Bruce's suggestion.

I am looking at converting a SQL Server based application with over 100 tables.