Tag Info

Hot answers tagged

4

AFAIK, using the existing services; it is not possible to access the content database informations from Client Object model or services. As a work around you can create your own WCF service and deploy it in SharePoint, which can provide your required data. How to Customize WCF Services in SharePoint 2010 SharePoint 2010: Create Custom WCF Service


3

If you have the old db-server up and running, use the following command in PowerShell: Get-SPSite -ContentDatabase <SourceContentDb> | Move-SPSite -DestinationDatabase <DestinationContentDb> This command moves all site collections from the source content database to the destination content database. Reference: Move site collections ...


3

As per the Microsoft KB articles, which applies to all SharePoint Versions, always against direct access to SharePoint database. here are the supported scenarios: Supported database modifications Exceptions to the prohibition against database modifications are made for specific usage scenarios: Operations that are initiated from the SharePoint ...


3

READ COMMITTED SNAPSHOT ISOLATION is not supported by SharePoint. Review the presentation below by Lisa Gardner from the PASS Summit back in 2012 for more details. http://blogs.msdn.com/cfs-filesystemfile.ashx/__key/communityserver-components-postattachments/00-10-36-86-42/SQLNSharePoint_5F00_Frienemies.pptx


2

You have to configure a custom BDC model, external content type, and then an external list. There is a really good article at C# Corner on the topic. Here are the steps at a high level: Using VisualStudio create new Project of type SharePoint 2010 > Business Data Connectivity Model. Modify the default Entity from the BDC Model to fit your view. Build the ...


2

You can't attach two copies of the same content database in the farm because the various GUIDs will be the same. Unfortunately the error messages you get when you do this are not especially helpful. The workaround for this is to create a temporary farm somewhere and attach the database there - then back it up from that farm. This gives you a fresh set of ...


1

When upgrading to SharePoint 2013 from 2010, you can choose to move only your content databases or you can upgrade some of your old services as well. The services that you can upgrade is the following: Secure Store service application Business Data Connectivity service application Managed Metadata service application User Profile service application ...


1

As You said, you dont want to use Kwiz solution in 2013. You have to remove/ uninstall that solution in 2010 completely. this way all refrence from content database gone. I highly recommend you to remove the twitter add-on as well. make it clean migration. Once you removed both then run the test-spcontentdatabase to check the potentail issue. If nothing ...


1

It depend what type of plan you have, if you have E3 or E4 then you can access the external data source. here is the great office article which explain what you can do it with external data source. Oracle is one of the supported database listed. http://office.microsoft.com/en-us/sharepoint-server-help/introduction-to-external-data-HA102891586.aspx other ...


1

Keep your ALIAS as is. In your web.config change all your connection strings for your custom web-parts/apps to point to the IP address of the SQL server.


1

If you are able to identify which web.config settings should point to SQL1 and which should point to SQL2 then you should change the respective values to point to the correct alias (yes you can have both SQL1 and SQL2 aliases side-by-side pointing to different database servers). However, you can't route SQL traffic to a specific server from one alias. Think ...


1

Yes it is compatible with SQL Server 2008 R2 SP2. Also check: http://social.technet.microsoft.com/Forums/sharepoint/en-US/45f3d039-3e98-4791-a9da-bcd80ad71835/sql-server-2008-r2-sp2-and-cu2-are-compatible-for-environment-sharepoint-server-2010-sp1


1

Provided that BCS is connected to the web service and not to the DB directly, you should not need to worry about any changes at all.


1

You will be out of support of Microsoft. I dont think we can predict what will goes wrong as its depend what you change/ add/delete? Microsoft cannot reliably predict the effect to the operation of these products when parties other than the Microsoft SharePoint Development Team or Microsoft SharePoint Support agents make changes to the database schema, ...


1

The scenarios you could use with SharePoint are: Save the database file in SharePoint itself and check it in and out when you're using it just like you'd do with any other file. This is kind of rickety and SP isn't really going to do a great job of telling you what changes you made, but it's possible, I guess. Use Access Services to, in essence, host the ...


1

You may be able to use SharePoint Web Services' Lists class to interact directly with your lists. It has methods to create and read items from lists in SharePoint.


1

no need for any of those! you just need to add it to web.config http://msdn.microsoft.com/en-us/library/jj653752(v=vs.110).aspx and http://msdn.microsoft.com/en-us/library/ms228094(v=vs.85).aspx somthing on the lines of: <appSettings> <add key="SQLConnectionString" ...


1

Well best would be to avoid the Access DB layer, SharePoint -> List is the best way.. But if its necessary, you can write a Custom WCF Service, call this service from InfoPath form.. And use C# to add contents to Access Database.. You can use Business Connectivity Services: External Lists to connect to Access Database and show the List View. Let me know if ...


1

It's not possible to create Web Access databases in SharePoint 2013. It is, however, possible to continue to use a Web Access database created in a 2010 environment. So the answer to your question is; it can't be created, but you can continue to use web access databases created with SharePoint/Access 2010. Access web databases are supported for backward ...


1

Here's a crazy idea: keep the alias, and for your custom SQL DBs, use the IP of the SQL Server in your web config that those web parts use. That way you bypass the alias that is borking your custom DB pointers.


1

It's not ideal, however the best way (in my experience) would be to use multiple aliases to help simplify this issue. One possible workaround could also be to update the SharePoint servers host files to point the db server names to the new IP address(es). The hosts file overwrites DNS entries, and is located in C:\windows\system32\drivers\etc\hosts. The ...


1

As the change in the allocation should not require a SQL restart I would guess that you have something else hogging the rest of the RAM. Look into the Proccesses tab and see if the culprit is visible there. As a best practice, nothing except SQL should be running there.


1

I have also this error. In my case solution was simple: If your SQL Server has 'Named Instances' you should write full name including your machine name: MY-MASHINE\MY-SQLSERVERNAME


1

if you goto central admin>upgrade and Migration> review database status. Once you have tyhe databses that need to be upgraded you can either use products config wizard or open a sharepoint powershell up (in admin) run upgrade-spdatabase -identity If you need the UID run get-spdatabase copy the UID for the database needed if you want to test this do a ...


1

I would say that the problem isn't a SharePoint problem (SharePoint is really speaking just a ASP.Net website reading and writing to a SQL database), but more of a SQL Problem. I found a good article where Microsoft did some research on the topic. Read here: http://research.microsoft.com/pubs/64525/tr-2006-45.pdf


1

It is possible that your server was configured using one database but then changed to point elsewhere for content which would mean that the original databases used for config and service applications still point to the old instance. If you open the SharePoint Management Shell and run Get-SPDatabase | Select Name,Server it will list all of the databases in ...


1

SharePoint never lies :) Could there be another SP Environment using the other database server? How does the DBA know it's your SP environment is using those databases? It could also be a DNS issue, does your SP server ping the correct IP for the SV002 server?



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