No. I suppose you could set up an instead of insert trigger which checks the number of rows and then rejects the insert if it is more than the number you want, but why exactly do you care how many rows the table has if the data is all valid data?
You could set the Max size the DB can grow to suppress filling the disc in case of an error, but that will also create issues when the DB reaches that max and no application or user can change the data.
You could create a second file group, put a file in it that can only grow so much, then put this table in that file. But again, if the file fills the insert query will fail.
Denny
--Anything is possible. All it takes is a little research. (Me)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.