Tag Info

Hot answers tagged

11

There are lots of point to discuss before coming to a conclusion here. But I will just explain the different possible ways you could do backup in SharePoint in an order of good to best. Central Admin Backup - This is a default UI option that comes within Central Administration. It allows to take full and differential backups. You have the additional ...


9

The TechNet Article "Storage and SQL Server capacity planning and configuration (SharePoint Server 2010)" should be your first port of call: http://technet.microsoft.com/en-us/library/cc298801.aspx


8

Definitely don't want to go the SQL query route because you can easily create an ineffecient query if you don't understand the underlying data model...also possible that you'll develop a query that breaks or becomes inefficient after a CU or SP is applied. CAML queries are very efficient and depending on the scope of your query you have a lot of options. ...


7

I discovered that the problem comes from the program Microsoft Visual Studio 2010 Shell (Isolated) - ENU that gets installed with SQL Server 2012. After uninstalling that program and then running the SharePoint 2013 installer I am able to see the splash screen. Warning - This will prevent Sql Server Management Studio 2012 from working on that machine.


6

The SharePoint_Shell_Access role gives you access to the content databases and the configuration database, and permission to execute the stored procedures. The farm administrator (not to be confused with the farm account) does not automatically have access to the content dbs. It can also grant you the role of "difficult SharePoint person" from the ...


6

The biggest determining factor here between SharePoint Backups and SQL Server backups is going to be how much content you have in your farm. Based on what I could find on TechNet, SharePoint backups are not supported for content databases over 200 GB in size (http://technet.microsoft.com/en-us/library/cc262787.aspx) and site collections over 100 GB in size ...


5

Something to be aware of along with SQL aliasing is the SQL instance. There are instances where if patching hasn't been applied, features and services within SharePoint will not configure properly on named instances. This you can also bypass using SQL aliasing. Personally, I am a proponent of SQL Aliasing, but you should always make sure that you configure ...


5

Microsoft licensing can seem complicated if you are doing that for the first time and I would advise you to contact a licensing specialist in your country/region that can help you optimize for best price and licensing deals. For a company of 10000 people you should not be checking these prices online, you need to talk to licensing specialist! Chances are you ...


5

First thing you should do is choose the appropriate recovery model for your databases. If you need point in time restore, go for the FULL recovery model. The price you have to pay is to make regular log backups or your logfile will grow indefinitely. Taking a full backup does not stop them from growing. If you use mirroring or log shipping, you also need to ...


4

Which version of SharePoint. If you're using SharePoint 2010, the easiest way is an external list with BCS through SharePoint Designer. http://msdn.microsoft.com/en-us/library/ee557243.aspx Paul.


4

It is not supported and unfortunately it is not going to be possible for you to make it work unless you run some sort of virtualization platform on top of Windows Server 2003. SharePoint 2010 requires Windows Server 2008 or Windows Server 2008 R2 as its base OS. It will work with SQL Server 2005 as long as you have it patched to the correct level (at least ...


4

Unless specified otherwise in your connection string, your timer job will connect to the database using the credentials your Timer Service is running under, not the interactive user. So make sure the Timer Service account has the appropriate privileges.


4

I believe it's permission related, we didn't have as much resistance in doing that here, but I think the reason is this: In order to use PowerShell, an administrator must be assigned the SharePoint_Shell_Access role on any databases against which PowerShell will be used. For example, to perform tasks that read or manipulate data in the ...


4

Here are some details about support for large databases with SP1. http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=988 Officially there is support up to 4TBs with optimization, but realistically that is difficult to support and should only be used in extreme exceptions. Technically there were no real changes made to support the additional ...


4

Simplest answer is: No. Similar issue (follow first link provided in answer): SharePoint License for Database Server Look also at comment by Jesus Shelby The only exception would be if you are running Reporting Service in integration mode, then you would have SharePoint installed alongside the SQL instance hosting the report server.


4

As long as you name your 2010 configuration database differently than your 2007 config db, you should be fine. In general, I'd recommend making an effort to name all the databases for your 2010 farm in a way that you can easily distinguish the databases for each farm. Or, you could create a separate database instance on your SQL Server host and point your ...


4

Doing the SQL Server backup of the content databases is almost identical to what you are doing with the PowerShell script: protecting your content. This is of course the most important thing that you will want to protect. The advantage that doing these backups through a maintenance plan on SQL gives you is that you can perform both full and differential ...


4

I have never done it personally but Microsoft has a document that lays out the steps pretty clearly. As always, be sure to take a good backup before attempting this.


4

It's not the prerequisites installation which selects sql, but the SharePoint installation. To run on a real Sql Server select Server Farm and then Complete, NOT Standalone or Stand-alone: When you then run the Configuration Wizard you are prompted to select the SQL server: Images taken from How to Install SharePoint 2010 on Small Farm – Part 1: Full ...


4

You should be backing up and truncating your TLOGS. If you have not been doing that, than yes, do a backup, truncate, and shrink will restore space. To keep that space however, you will need to set growth limits on your database and log files. Microsoft has a paper on "best practices" with SQL maintenance: ...


4

Minimal is SQL Server 2008 Express with SP1. The main difference with Standard is you can have a larger than 4gb database. So the answer is yes. Comparisons here


4

No. IIS is only for serving up webpages. It should not be part of SQL Server, which uses tcp/ip, or named pipes to communicate with other servers.


3

The server collation must be configured for case-insensitive, which is ok in your case. If you use SharePoint itself to create its different databases, it will set the required collation automatically. However, if you use precreated databases - make sure you to change the collation manually. Otherwise, SharePoint won't even let you use those databases.


3

Here are a few resons on why to upgrade Upgrade to SQL Server 2008 R2 - performance and availability SQL Server 2005 mainstream support will end fairly soon (read more at http://support.microsoft.com/gp/lifesupsps) Security Better Reporting Services


3

You can use the SQL alias tool (cliconfg.exe) on your server to just create an alias with the original servername, and then point it to the new one. This way SharePoint will not be aware of the changes, but will hapilly connect to the new server. Even if you don't want to change to a new server right away, you can still use it to introduce an alias - ...


3

You could do this without code by using BCS to connect to your SQL table with 2 way data update support, and use a workflow to transfer your sharepoint list to the external list (which would then write to your SQL table via BCS).


3

I would like to add a biggie to your list of common problems admins hit: The need to move the SharePoint farm to a different database server. SharePoint 2007 (not sure about 2010) does not like it when you change database servers. There are numerous articles out there about how to move your farm to a new server, but the big gotcha in doing it is that you ...


3

I just installed SSE 2010 and it is SQL Sever Express 2008 SP1. (Build 10.0.2531.0) So to avoid the 4 GB limit for content DBs I'd recommend to download and install SQL Server Express 2008 R2 and do a farm install instead of a single server install. This moves the limit to 10 GB. If you can afford the license cost, it is also possible to use a full version ...


3

You probably don't have proper permissions on the SQL side. Add your login as the SQL administrator or grant the permission directly on the databsae WSS_Content, for example db_owner role. UPDATE: This should help You: Link but You should select "Windows authentication" and YOu should search for Your login name MYDOMAIN\mylogin_id



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