2 tables differ from Microsoft's tables

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for MySQL
Post Reply
Posts: 4
Joined: Sat 25 Feb 2017 01:12 2 tables differ from Microsoft's tables

Post by njb » Sat 25 Feb 2017 01:21

Our application uses the .net 2.0 membership provider and we are attempting to switch off of Microsoft and onto MySql. I have downloaded the free 30 day trial of dotConnect for MySQL and have run the InstallWebTables.sql file found in dotConnect/MySQL/Web/ASP.NET 2. What I find is that the aspnet_roles table differs significantly from what we find on our MSSQL boxes.

The MSSQL side has the following schema:

Code: Select all

CREATE TABLE [dbo].[aspnet_Roles](
	[ApplicationId] [uniqueidentifier] NOT NULL,
	[RoleId] [uniqueidentifier] NOT NULL DEFAULT (newid()),
	[RoleName] [nvarchar](256) NOT NULL,
	[LoweredRoleName] [nvarchar](256) NOT NULL,
	[Description] [nvarchar](256) NULL)
The InstallWebTables.sql file has this schema:

Code: Select all

CREATE TABLE aspnet_roles (
  applicationname VARCHAR(255) NOT NULL,
  roleid VARCHAR(40) NOT NULL,
  rolename VARCHAR(245) NOT NULL,

  CONSTRAINT aspnet_roles_roleid_pk PRIMARY KEY (roleid),
  CONSTRAINT aspnet_roles_rolename_key UNIQUE (rolename, applicationname)

Why are these two tables so different and how should we go about converting the data from MSSQL to MySql in this case?


Devart Team
Posts: 2138
Joined: Wed 02 Nov 2011 09:44

Re: 2 tables differ from Microsoft's tables

Post by Pinturiccio » Tue 28 Feb 2017 15:36

dotConnect for MySQL ASP.NET 2.0 tables differ from the corresponding tables of the SqlClient provider. For example, dotConnect for MySQL doesn't require stored procedures, unlike SqlClient.

You just need to migrate data from the tables, and it should be enough for working with dotConnect for MySQL.

Unfortunately, we don't have an experience of migrating data from the tables, created by the SqlClient Role provider to ASP.NET tables of dotConnect for MySQL.

Post Reply