I would like to know and understand if MS Dynamics CRM 2013 Online can have an ON-PRIM DB. My application (MS CRM 2013) will reside on MS Cloud however the data will reside on my on-prim instance. (Typical hybrid scenario).
Is this kind of implementation supported by MS Dynamics CRM 2013 Online?
No, CRM Online can't use your On-Prem DB.
Really, the only way would be a hosted Dynamics (on-premises) instance installed in the cloud, say in Azure on standard virtual servers, then having a VPN between the cloud server and the in-house DB server.
Not strictly speaking MS Dynamics CRM 2013 Online, but would allow you front-end to be in the cloud whilst your data is all on-premises. It's also worth noting that, due to latency, this setup may experience performance issues.
Not possible - CRM hosts its own DB. Azure will only let you host custom code, which you can use as SOA app. server on Cloud.
Related
so I don't know a whole lot about Office 365 and have been learning other frameworks that do not include ASP.NET.
The company I work for is using is Office 365 and CRM. I read you can interface CRM with a web app. What I am wondering is if a company had a web application they used on their intranet, is it possible to migrate it to Office 365? Possibly as a Site? Is it possible to develop a web app that shows up under Office 365 and is therefore accessible to employees at that Office 365 account? You would need access to the MS SQL and IIS web server running, can you get that kind of access through Office 365?
The answer is yes, you can have your application hosted on Azure or anywhere with all you backend and host it as an App in o365.
What i suggest you to do, Get Office Development tools for VS 2015, just create a project from under Office/SharePoint section and select SharePoint Add-In project template and check out the created project. you will see that an asp.net web project has been created and another project as a shell for deploying this app as SP app. you do have the option to host this app anywhere :)
Check out this tutorial: https://msdn.microsoft.com/en-us/library/office/fp142379.aspx
Hope this helps.
Yes - you can build a web application and have it appear in the Office 365 app launcher. However, there are some specific architectural requirements such as integration with Azure AD and single sign-on.
Have a look at this article: https://msdn.microsoft.com/en-us/office/office365/howto/connect-your-app-to-o365-app-launcher?f=255&MSPPError=-2147217396
I'm evaluating the IT-Hit Webdav component. Their Delta-V server sample is my starting point. If I open a word document directly from a Sharepoint site, MS Office shows a button which enables me to check out the document if needed. While using the IT-Hit server doesn't provide this feature for MS Office. It is important for us, that our own WebDav sever created with IT-Hit provides the same features as Sharepoint does.
Am I doing something wrong, or is this just not possible?
Rgards
Microsoft SharePoint and Microsoft Office are using a bunch of proprietary SharePoint protocols for comunication, they are not using DeltaV. IT Hit WebDAV Server Engine does not implement that Microsoft protocols. Therefore you can not achieve the same functionality only implementing DeltaV or using DeltaV sample.
The only server that implements Microsoft SharePoint protocols as far as I know is Alfresco.
I need to develop a dynamic web page retrieve data from a stored procedure on a SQL Server.
Considering the licensing issue, development resources, security and maintainability, can someone suggest a suitable platform for this project?
I have a Ubuntu server running Drupal and also a Windows Server 2003 running SQL Server 2000 and IIS for FTP server only.
Is ASP.NET and Reporting Service the natural choice? What are my other options? Ruby On Rails? Since the SQL Server on the server is mission critical and I don't feel very comfortable asking anymore from it.
SSRS is very good for the price; though in SQL 2000 its a bit limited - especially for charting. If you have a small budget you could write nice looking reports using stored procedures and something like telerik reporting if you want to do a bit more of the work on the web server. There is a trial version you could use for a quick prototype to see how it fits in; but it works very nicely with asp.net development and is nicely integrated with Visual Studio.
I have a partly developed asp.net application, but now the client wants it to be developed in azure. How much of the existing code can be used in developing the application in azure.
What challenges could we possibly encounter when we try to port an existing asp.net application to azure? Are there any other alternatives to azure in cloud computing?
For an asp.net application, you can certainly port that to Azure. Your core logic will port in a relatively straightforward manner, and you'll gain the many benefits Azure has to offer. With the June 2010 release, you'll also have .NET 4 support, along with IntelliTrace for debugging.
However, as you begin to plan your Azure migration, there are several considerations you'll need to think about (none of them insurmountable, and several relatively simple to deal with):
You have to deal with ASP.NET Session State management across your web role instances (which isn't supported out of the box, except for inproc). You'll also have to set up and use the role and membership providers (see here for more detail). EDIT: You now have access to both AppFabric Cache for session state as well as SQL Azure, part of the Universal Providers included with the Windows Azure SDK+Tools.
You have to examine your SQL backend for incompatibilities with SQL Azure (such as scheduled jobs,since there's no SQL Agent support). SQL Azure differences are documented here. You'll also need to consider the SQL Azure size limit of 50GB, which might require you to offload content to Azure blob storage. EDIT: You can run your SQL Server database through the SQL Azure Migration Wizard for compatibility-testing.
You need to configure logging and diagnostics, preferably with Trace output, so that you can retrieve this data remotely.
You need to think about how you'll monitor and scale your application. All information you might need for scaling is available to you (performance counters, queue lengths, etc.). Check out WASABI - the auto-scale application block, part of Enterprise Library. You can also subscribe to a service such as AzureWatch.
You'll need to think about caching, as there's currently no out-of-the-box caching implementation that runs across instances of your web role which is now provided as a service. Read details here, as well as an FAQ here.
Do you need SMTP support? If so, there are details you should read about here. SendGrid recently announced a free-tier promotion for Windows Azure.
Are you hosting WCF services as well? If so, check out this site for further details (specifically the Known Issues).
So: yes, there are some things you need to concern yourself with, but Azure is a great platform for hosting an asp.net application and you should strongly consider it.
It should be very easy to port your application to Azure--especially if you're using a SQL back-end. The code could run almost without modification. You'll need to create an Azure installation package for the project and configuration file.
If your application makes use of persistent storage (other than SQL Server), you may have to rework that code somewhat. However, the platform now has drive storage, which simulates a file system, so this should be fairly easy.
Another issue to watch out for is web.config. If you make heavy use of this for runtime customization, you'll have to rework that too. You can't deploy single files to your application in Azure, so the recommended approach is to migrate these sort of settings to the Azure config file.
The hardest thing you're likely to encounter is external applications. If your app relies on launching other processes, then this will require some serious redesign.
Azure now supports Web Sites as a deployment type. Basically this allows you to publish any standard Asp.net (and other supported like PHP etc) application to Azure and have it as a scalable server. See this article http://blog.ntotten.com/2012/06/07/10-things-about-windows-azure-web-sites/
Many of the benefits of Azure without having to introduce Azure specific code/Project to your existing application.
Also this question here What is the difference between an Azure Web Site and an Azure Web Role
Client has a bunch of Access databases and associated reports.
He wants to make the reports available (live, not snapshots) via a secure extranet.
He's willing to recreate the reports using a proprietary GUI if necessary, but ideally would like a solution that exports his reports "as is" to the web.
Had a look at Caspio Bridge. It's pretty slick but doesn't appear to offer grouping and summing (key requirement) without a nasty Javascript hack - seems like a rather glaring omission to me!
Any suggestions?
I'm an ASP.NET developer so if there's coding involved, an ASP.NET based solution would be preferred.
You can try Access Reporter.
http://www.ssw.com.au/ssw/AccessReporter/Default.aspx
You might like to consider Access 2010, point 3 of the linked document says:
Access your application, data, or
forms from virtually anywhere.
Extend your database to the Web so
that users without an Access client
can open Web forms and reports via a
browser and changes are automatically
synchronized.1 Or work on your Web
database offline, make your design and
data changes, and then sync them to
Microsoft SharePoint Server 2010 when
you’re reconnected. With Access 2010
and SharePoint Server 2010, your data
can be protected centrally to meet
data compliance, backup, and audit
requirements, providing you with
increased accessibility and
manageability.
-- http://www.microsoft.com/office/2010/en/access/default.aspx
SQL Server Express edition is free. It includes Reporting Services
http://www.microsoft.com/Sqlserver/2005/en/us/express.aspx
You can connect to the MS Access database (or any other database that you have OLEDB or ODBC connectivity for)
For your existing reports, here is a link on how to migrate just the reports to SQL Server (leave data in MS Access)
http://technet.microsoft.com/en-us/library/cc966391.aspx
Actually, the suggestion being given here is to move your back and data up to SQL server , but keep your front end application part as is in Access.
So the suggestion isn’t to move your application to SQL server. The suggestion here is to move only the data part of your application to SQL server but continue to use the desktop access application.
So, you link your tables to sql server, and continue to use the access application.
What this means that is you can use SQL server reporting services, or some other web based interface that pulls the data from SQL server. So your access application will be directly updating the data on that SQL server.
This setup works well since you not tying to shuttle data between two separate systems. I know a number of companies that successfully migrated their backend data to SQL server for this very purpose of allowing the Executives and the company Managers to view reports on a web based system.
However, they did not have to throw out or lose the investment and time they spent building the access application part.