I'm getting an error that is puzzling to me. I set up transactional replication to 3 new SQL 2012 database servers for use as read-only servers. I did not replication indexes, but created them on all 3 servers after the tables were all replicated. The replicated database was set to auto-grow on all servers with no maximum, and the servers all have a SAN LUN apiece for data and logs and a local SSD RAID 1 array for tempdb. All drives have something like 80% free space.
I have a SQL Agent job that runs daily that reorganizes or rebuilds all the indexes as required. Whether the index is touched, and whether it is reorganized or rebuilt is determined by the percentage of fragmentation. When I ran the job on one of the servers for the first time as a test, I got the error below for all the tables:
“Could not allocate space for object 'xxxx' in database 'xxxxx' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.”
As I said, the database is set to no autogrow with no limit, but on the assumption that maybe the server could not allocate new space fast enough, I reset the initial size of both the data and log files to twice their current size. That did not fix the issue either and I still get the errors when the task is run on any of the servers for the first time, and I assume the issue will recur once the indexes become fragmented again.
Thanks in advance for any help you can give.