Will changing the database schema of a feature class that is published as a feature service "break" the service?
I have deleted and recreated relationship classes and the service does not work unless it is republished. What about adding and deleting fields? If this is the case, is it a best practice to only have one feature class in a service so as to not have the service with multiple feature classes break because of a schema change in one of the classes?
I think I just answered my own question but would like an expert opinion.