This question is locked. New answers and comments are not allowed.
Hi
I am looking forward to write a web-app. that can run on both the traditional and Azure servers. How could Open Access ORM help me in this case, can I just write to the Open Access API and Open Access run-time will be able to handle both? Or, do I need to take care of the differences, if any?
With Regards
I am looking forward to write a web-app. that can run on both the traditional and Azure servers. How could Open Access ORM help me in this case, can I just write to the Open Access API and Open Access run-time will be able to handle both? Or, do I need to take care of the differences, if any?
With Regards
3 Answers, 1 is accepted
0
Hello Raman,
You do not have to care about differences, we do that. But the SQLAzure server gets more and more functionality, in the meantime there is no difference in the handling any more. With our new database creation and migration API you are even able to manage the database schema directly via OpenAccess in your application. (context.GetSchemaHandler())
All the best,
Jan Blessenohl
the Telerik team
You do not have to care about differences, we do that. But the SQLAzure server gets more and more functionality, in the meantime there is no difference in the handling any more. With our new database creation and migration API you are even able to manage the database schema directly via OpenAccess in your application. (context.GetSchemaHandler())
All the best,
Jan Blessenohl
the Telerik team
0
Raman
Top achievements
Rank 1
Rank 1
answered on 28 Jan 2011, 05:47 PM
Hi Jan
Thanks for the reply. This is good news. Once again, I want to make it 100% clear.
So this means that you offer a consistent/same API for both the SQL DB and Azure platforms. Correct?
If yes, we'd be able to run the app. that accesses the db using the OpenAccess ORM on a platform of our choice whether it be Windows/SQL Server OR Windows Azure? Pl. confirm.
>But the SQLAzure server gets more and more functionality.
What do you mean by this? Pl. elaborate.
What else do we need to take care of while writing the ASP.NET app. using Telerik RAD Controls if we want to make it cloud-enabled, any ideas. I read that we avoid maintaing the session state. If yes, where shall we store it?
I also read that Telerik RAD controls can be used in both the Azure and Traditional environments.
With Regards
Raman
Thanks for the reply. This is good news. Once again, I want to make it 100% clear.
So this means that you offer a consistent/same API for both the SQL DB and Azure platforms. Correct?
If yes, we'd be able to run the app. that accesses the db using the OpenAccess ORM on a platform of our choice whether it be Windows/SQL Server OR Windows Azure? Pl. confirm.
>But the SQLAzure server gets more and more functionality.
What do you mean by this? Pl. elaborate.
What else do we need to take care of while writing the ASP.NET app. using Telerik RAD Controls if we want to make it cloud-enabled, any ideas. I read that we avoid maintaing the session state. If yes, where shall we store it?
I also read that Telerik RAD controls can be used in both the Azure and Traditional environments.
With Regards
Raman
0
Hi Raman,
OpenAccess offers the same API and functionality against all support backends. You can even switch to oracle.
The SQLAzure server was reduced in functionality compared to SQL2008R2 but they allow now everything OpenAccess needs to perform well.
The cloud machines are billed by looking at the traffic, memory and CPU usage. This means if you reduce the traffic between browser and server it is good, if you reduce the memory usage, it is also good. I do not think that you should avoid session state, you just have to prepared that your process is moved to a different machine without notification and you loose your session state more often.
Regards,
Jan Blessenohl
the Telerik team
OpenAccess offers the same API and functionality against all support backends. You can even switch to oracle.
The SQLAzure server was reduced in functionality compared to SQL2008R2 but they allow now everything OpenAccess needs to perform well.
The cloud machines are billed by looking at the traffic, memory and CPU usage. This means if you reduce the traffic between browser and server it is good, if you reduce the memory usage, it is also good. I do not think that you should avoid session state, you just have to prepared that your process is moved to a different machine without notification and you loose your session state more often.
Regards,
Jan Blessenohl
the Telerik team