Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am trying to alter a table field – with some rows in it – from DateTime to DateTime2(3).
But the SQL Server Management Studio complains that I have drop and re-create the table.
But why?
Isn’t DateTime2(3) has more precision than DateTime type? It should be fine, should not it be?
There is a setting in SSMS that will allow you to do what you want.. Menu-Tools-Options-Designers-Prevent saving changes that require table re-creaction.
SSMS has a habit of recreating almost any changes you do. It should be just fine to only alter the column data type with something like this.