Tag Info

Hot answers tagged

6

Here are the pros and cons you were asking for. The biggest reason to use a SQL Alias over a cname is so that you can alias multiple instances on the same SQL Server. SQL Alias Pros Supports server/instance aliasing Server Admin can configure as needed. Does not require a domain admin No need to worry about DNS caching Nearly complete control over the ...


4

My preference is for a SQL Alias, as its something that I'll able to (hopefully) ensure that I have more direct control over its setup and settings than I would with a DNS entry. Sure, in a perfect world I'd have the rights to manage DNS in addition to installing and configuring SharePoint, but the reality is that in most cases as a consultant I don't have ...


4

Short answer: you can't. And why would you create the database using a feature? If you are creating an installer anyway, create the DB there using a db create script or a custom seetup action. As for storing the DB connectionstring and or DB credentials: Use the SecureStore Service Application. See this article for information on how to configure the ...


3

You can programmatically add/update AppSettings to the web.config file. You could store your connection string in an AppSetting string...


3

The title of your question implies that you want to configure the connection string for each web part. To do this, you should add a web part property to your webpart. Then the user that adds the web part to the page can fill in the value for the connection string. I assume you have a user control for your web part, so just assign your web part property to a ...


2

I believe a better question would have been... SQL Alias or DNS Alias? SQL Alias (AKA WINS) Benefits: Good to use if you are not a DNS administrator and you want to have full control over the alias setup. Drawbacks: You have to configure it on every SP server (WFE and APP servers) You have to install SQL Server add-in on non-SQL server machines ...


2

The OWSTIMER doesn't run in a web context and does not have immediate access to your web application web.config files. You can use something like this tutorial to read web.config values from your web apps: http://praveenbattula.blogspot.com/2009/12/access-webconfig-in-sharepoint-timer.html You can also create an app.config file right next to the ...


2

BCS is great for rapid connection to an external datasource through SPD. And as you say: with it you can use the OOTB list WebParts etc. and als have have direct access even through the OData API. Without writing a single line of code. In SP2013 you even have the possibility to register Remote Event Receivers. Aswell as security features not to forget. So ...


2

Quite a big question. Here's my take on it. In SharePoint land there is a clean separation between admin level stuff and content level stuff. Admin level stuff is created using features at the farm or web application level. Things like IIS, backup restore, search configuration, etc... Content level stuff is commonly defined in features too, site collection ...


1

For connecting fields to external data you can best use Business Connectivity Services (BCS). This way you can store your connection in a secure and central place in Cental Admin. With Business Connectivity Services, you can use SharePoint and Office clients as interfaces into data that doesn’t live in SharePoint 2013 itself. For example, this external ...


1

I would set up a Business Data Connectivity model to consume data from PostgreSQL and expose it in the form of an external list. There are plenty of tutorials on the internet on how to go about it, for example: http://raquelalineblog.wordpress.com/2013/05/19/sharepoint-2013-bcs-in-visual-studio-2012/


1

Ensure the user has rights to access the database Also ensure the connection file has been approved - A sharepoint admin can access a non approved Ucdx file. Go to the connection library and approve the file.


1

Strange it doesn't work. Just to be sure: you don't have to change anything in SharePoint. Just create an alias with the name SharePoint is referring to, but pointing to the server with the new server port: In this example, SharePoint thinks it's still connecting to DBSERVER at port 1433 but it actually connects to 123456 without knowing it. This article ...


1

Changing the default database DOES NOT change existing references. I recall in 2007 the config database was the only database you couldn't move (A backup had to be restored to the same name/server). You may need to check if this is still the case.


1

I havent done this before and would like to know how it goes and your solution. The solution i found sounds a bit long winded but solves the problem... if you read through there are two solutions you could try. I wish i could help you more but im no system admin but here is what iv found: solution 1: I think you many change the default server from ...


1

I don't know why but I had a problem with sql server which only accepted two connections at the same time. I increased this number and it was ok :)


1

Hmm. Since your SQL Server Service apparently went down as well, it seems the issue is less about SharePoint and something more systemic. Ideas: - check the UMLS and diagnostics logs in the SharePoint hive.There, you should find the source or details of your error. - go into your Windows Services. (Adminstrative Tools -> Services). Check to see that your ...


1

You can create custom property for the feature. In your Feature CAML you can define <Feature id...> <Properties> <Property Key="ConnectionString" Value="String"/> </Properties> </Feature> Then use this code in the feature receiver SPFeatureReceiverProperties.Feature.Properties["ConnectionString"] In this case ...


1

Is your SQL server running on the same server? If not you will run into the double-hop authentication issue and you will need to configure Kerberos. If SQL is on the same box and you have SharePoint configured for Windows Integrated authentication then integrated security should just work - no special configuration required.


1

Both External Content Types (to be precise, ECT is only a part of BCS - Business Connectivity Services) and DataSources (you can create them programmatically, not only through the SharePoint Designer) - can be used to connect external data to SharePoint. I'd prefer to use BCS when dealing with important external data. In long perspective, this approach ...


1

Function below (edited, will not compile) get the Web Analytics connection for given SPSite /// /// get Connection string to Web Analytics database /// /// /// public static string GetWAConnectionString(SPSite site) { string sConnectionString = ""; //get web analytics proxy type ...



Only top voted, non community-wiki answers of a minimum length are eligible