none
Project server 2010 What are the number of Custom fields and views allowed? RRS feed

Answers

  • While there is no hard limit, you'll start hitting performance and usability issues with a large number of custom fields (hundreds+), especially with a large number of calculated ones.

    www.umt.com

    Friday, April 26, 2013 2:07 PM

All replies

  • While there is no hard limit, you'll start hitting performance and usability issues with a large number of custom fields (hundreds+), especially with a large number of calculated ones.

    www.umt.com

    Friday, April 26, 2013 2:07 PM
  • Thanks for your help Catalin.
    Monday, April 29, 2013 4:44 AM
  • Hi

    you might be able to create as many custom fields as you like. (I think the marketing gurus said something like "unlimited custom fields" when the hard Limit fell with Project Server 2007).

    But apart from the performance issue you will have an issue, if you need to pull reports from your data. The project user view that contains builtin and custom fields does a join per custom field - and there is a hard limit (as I believe) of 250 joins in SQL Server. So you will have difficulties to Report on your data, if you have 300 project custom fields.

    Regards

    Christoph


    Christoph Muelder | Senior Consultant, MCTS, MCSE, MCT | SOLVIN information management GmbH, Germany

    Saturday, May 24, 2014 8:04 PM
  • You can also refer to the typical dataset versus performance recommended by Microsoft:

    http://technet.microsoft.com/en-us/library/hh297440(v=office.14).aspx


    Hope this helps,


    Guillaume Rouyre, MBA, MCP, MCTS |

    Saturday, May 24, 2014 8:20 PM
    Moderator
  • Hi

    new findings on that issue...

    There is an article for Project Online that speaks about limits for reporting: https://support.office.com/en-US/Article/Project-Online-software-boundaries-and-limits-5a09dbce-1e68-4a7b-b099-d5f1b21ba489?ui=en-US&rs=en-US&ad=US

    Apart from that you will have an issue if you like to upgrade to Project Server 2013. When trying to convert the 2010 databases to a 2013 database a SQL stored procedure will fail if you have more custom fields than fit into the UserViews.

    Error message will be something like this:

    System.Data.SqlClient.SqlException (0x80131904): INIT METADATA ERROR!  At least one mismatch found between SQL schema for view MSP_EpmProject_UserView and reporting metadata.  Call to MSP_Epm_CheckIntrinsicAttributes failed for Projects  INIT METADATA ERROR.    
     at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)    
     at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)    
     at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)    
     at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)    
     at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite)    
     at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)    
     at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)    
     at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()    
     at Microsoft.Office.Project.Server.Data.SqlSession.ExecuteNonQuery(SqlCommand command)  ClientConnectionId:21f11abd-7388-48a0-a029-b5161fcb2dc8

    Workaround for the issue (UNSUPPORTED !!!!!!)

    Execute the Convertto-SPProjectDatabase script. Now you need to be fast or well prepared. You need to find the MSP_Epm_CheckIntrinsicAttributes stored procedure. Execute an ALTER statement for it and change the last lines of code to something like this:

    ...
    LblError:
       PRINT @ErrorMessage
        --changed RETURN code if an error occurs to be able to proceed with migration 
        --RETURN 1
         RETURN 0
    END

    I hope that helps someone out there - when I came across the issue last night, a google query returned nothing for INIT METADATA ERROR....

    Regards

    Christoph


    Christoph Muelder | Senior Consultant, MCTS, MCSE | SOLVIN information management GmbH, Germany

    Thursday, October 9, 2014 10:46 AM