Could not allocate memory for Change Data Capture population. Verify that SQL Server has sufficient memory for all operations. Check the physical and virtual memory settings on the server and examine memory usage to see if another application is consuming excessive memory.
Could not add new article to publication '%1!s!' because of active schema change activities or a snapshot is being generated. ...
Could not allocate a new page for database '%1!s!' because of insufficient disk space in filegroup '%2!s!'. Create the necessary ...
Could not allocate ancillary table for view or function resolution. The maximum number of tables in a query (%1!s!) was exceeded. ...
Could not allocate enough memory to start the Service Broker task manager. This message is a symptom of another problem. ...
Could not allocate memory for Change Data Capture population. Verify that SQL Server has sufficient memory for all operations. ...
Could not allocate memory for the log reader history cache. Verify that SQL Server has sufficient memory for all operations. ...
Could not allocate space for object '%1!s!'%2!s! in database '%3!s!' because the '%4!s!' filegroup is full. Create disk space ...
Could not alter column '%1!s!' of change table '%2!s!' in response to a data type change in the corresponding column of the ...
Could not automatically discover any SQL Server instances. Choose Register SQL Server Instance from the shortcut menu if ...