Codepolice.net » SQL Server http://codepolice.net C#, ASP.NET, MVC, LINQ, Wordpress and stuff like that Mon, 26 Jul 2010 08:58:47 +0000 en hourly 1 http://wordpress.org/?v=3.0 SQL Server: Saving changes is not permitted because table will be re-created http://codepolice.net/2009/09/10/sql-server-saving-changes-is-not-permitted-because-table-will-be-re-created/ http://codepolice.net/2009/09/10/sql-server-saving-changes-is-not-permitted-because-table-will-be-re-created/#comments Thu, 10 Sep 2009 09:52:35 +0000 Ola http://codepolice.net/?p=168 Microsoft has added a setting to Management Studio to prevent us from re-create tables when we make changes to them. I don’t like this settings and it would have be much better if they said ‘This table will be re-created, are you sure you want to do that?” instead of just stop us from doing it.

There is an option to turn this off if you go to “Tools -> Options -> Designers -> Table and Database Designers” and the uncheck the checkbox “Prevent saving changes that require table re-creation”.

sql_option

]]> http://codepolice.net/2009/09/10/sql-server-saving-changes-is-not-permitted-because-table-will-be-re-created/feed/ 0 ASP.NET membership: System.Web.Security. SqlRoleProvider problems http://codepolice.net/2008/12/16/aspnet-membership-systemwebsecuritysqlroleprovider-problems/ http://codepolice.net/2008/12/16/aspnet-membership-systemwebsecuritysqlroleprovider-problems/#comments Tue, 16 Dec 2008 21:18:46 +0000 Ola http://www.codepolice.net/?p=100 I had this really weird problem just now. I have done some work with the ASP.NET Membership provider and everything has been working great. But when i tried to deploy my application to the server i got this:

The ‘System.Web.Security.SqlRoleProvider’ requires a database schema compatible with schema version ’1′. However, the current database schema is not compatible with this version. You may need to either install a compatible schema with aspnet_reqsql.exe (available in the framework installation directory), or upgrade the provider to a newer version.

Alright, my database was exactly the same and everything looked fine. I tried to recreate my database with the aspnet_regsql.exe tool but nothing worked. Then i finally found this thread on the MSDN messageboard and one guy said that he gave his application a name in the aspnet_Applications table and put that name in the web.config like this.

<add connectionStringName="ApplicationServices"
applicationName="APPLICATION NAME"
name="AspNetSqlRoleProvider"
type="System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

And that solved it. Really really strange and i have no idea if this is a bug or whatever. On my local machine (Vista with IIS7) it worked great to have a application named “/” but on my production machin (a Server 2003 with IIS6) it did not.

Now i should stop working for today.

]]> http://codepolice.net/2008/12/16/aspnet-membership-systemwebsecuritysqlroleprovider-problems/feed/ 0