Install SharePoint 2013 client sdk in SQL production - sql-server

I am not a SharePoint person so please bear with me on my question. I have been asked to install the SharePoint 2013 Client Component SDK in a production SQL environment. I have been trying to research if there are negatives to doing this and cannot find that this is a common thing to do. Since SDKs are usually used for development and in almost 20 years of managing SQL Servers I have never been asked to install SDKs in a production environment I am thinking that this is not a good idea. Anyone have advice? Thanks!

The Client SDK of SharePoint 2013 deploy DLLs in the GAG of your server.
Microsoft.SharePoint.Client.dll, Microsoft.SharePoint.Client.Runtime.dll (as far as i remember) and some others client DLLs. So, there should not be any conflict with other MS product.
But, this sdk is needed by client application for SharePoint. Which means, you need to install a client SharePoint Application on a SQL server. If there is no problem with this. There is no problem with your install of the SDK.
PS: Client application for SharePoint can connect To SharePoint system everywhere (server, PC,..) so you can install this apps on an other server (or PC). but it depends on what the application makes
(sorry for my english)

Related

Google Cloud Compute engine - SQL Web 2017 missing ssis install

please help me out.
Trying to install feature integration services on VM MS 2019 SQL 2017 web edition server, but it is missing the install files. According to Google SSIS is to be included in web edition licence..
If not, how do I then upgrade my SQL edition..
Best
/Peter
As the above comment mentions, the integration services are not available for the web addition. Currently, there is no way to upgrade to another OS version within GCP. You will have to create a new GCE VM instance and choose the proper OS image to use.

what is the new approach to developing C# apps with a stand-alone database?

I'm looking into developing single deployment applications, traditional desktop applications with simple database(s) embedded. By my understanding Microsoft have removed support for MSSQL Compact Edition in the newer versions of Visual Studio.
I've read that the approach recommended by them is to use the Express version of MSSQL, however I'm failing to understand how an application with an Express SQL database embedded in it would be able to run on a machine without the SQL service installed and running.
Am I missing something here? I've hunted around Google for the last few hours, is the only solution to use a 3rd party technology like SQLite?

Setting up DB in client computer for WPF

I have a wpf application developed with VS2015 community edition. I'm done with the development. I want to test it in the client computer. The program uses SQL database. I installed Microsoft SQL in the computer where it was developed. How to setup a db in the client computer? Is there a easier solution other than azure or installing Microsoft SQL in the client's computer. I wish to publish it as a ClickOnce application. Please give a simple solution. Thank you.

Entity framework code first not creating database in vs2010

I’m new to vs2010 and the entity framework (and ASP.NET MVC as well....I’m from a winforms vs2005 background) as well as the azure platform and am starting a project using these technologies soon.
I’ve installed vs2010 and the windows azure sdk kit for vs2010 and am running through this tutorial, Deploying an ASP.NET Web Application to a Windows Azure Cloud Service and SQL Database.
http://www.windowsazure.com/en-us/develop/net/tutorials/cloud-service-with-sql-database/
I’ve got as far as the ‘Add SQL support’ section, followed the instructions and when I compile and run no database is being created.
And I’m using sql server 2008 r2.
Any ideas why this is the case? Nothing at all is being shown in the sql server log. My connection details look fine, am I missing some kind of add on or some permission settings need changing?
Cheers,
I've sorted this myself. If you wish to know the answers I've posted them in the comments on the tutorial page, just follow the link (names Mathew in the comments section).
http://www.windowsazure.com/en-us/develop/net/tutorials/cloud-service-with-sql-database/

Lightswitch prerequisites on ASP.NET webserver

I am trying to deploy a LightSwitch application to a hosted ASP.NET webserver in my company. The application access data stored on a SQL Server. My webserver admin is asking me if there are any special prerequisites needed for it to run. I've been reviewing the deployment guide
http://blogs.msdn.com/b/bethmassi/archive/2010/09/23/configuring-a-machine-to-host-a-3-tier-lightswitch-application.aspx
The article lists that there was a server component, but that it might change when RTM arrived:
NOTE: The team is looking at simplifying this process and possibly making the LightSwitch server component pre-reqs go away so this process will likely change for RTM.
This other MSDN article states that there are prerequisites.
http://msdn.microsoft.com/en-us/library/gg481779.aspx
My webserver admin keeps saying there's nothing to install on the ASP.NET web server other than .NET 4.0.
Am I missing something?
Server setup procedures haven't changed since Beta 1 (although of course the runtime has changed). It's pretty simple; the prerequisites article that you cited has the correct information. Basically the process is:
Install the Web Platform Installer if you don't already have it installed
Fire up the WPI and search for the LightSwitch runtime
Install!
As mentioned in the article, you'll need to decide whether you want to install a new instance of SQL Server locally with the prerequisites. If you've already planned for a production SQL Server, you'll want to choose the "without local SQL" option.
I don't have a specific answer, but I would stand up a VM with the appropriate version of windows server on it and run through an install on a do novo machine. Should confirm or deny what your server admin says . . .

Resources