chore: Made test for sql serve schema issue sql-server specific. I su…

…spect the failing tests indicate the bug is still present on other DBMS's, but I don't know enough to go chasing that right now.

unittests/TestCommon/Generic/Running_MigrationScripts/Versioning_The_Database.cs

@@ -95,32 +95,4 @@ public async Task Creates_a_new_version_with_status_InProgress()
         version.status.Should().Be(MigrationStatus.InProgress);
     }
 
-    [Test]
-    public async Task Bug230_Uses_Server_Casing_Rules_For_Schema()
-    {
-        //for bug #230 - when targeting an existing schema use the servers casing rules, not .Net's
-        var db = TestConfig.RandomDatabase();
-        var parent = CreateRandomTempDirectory();
-        var knownFolders = FoldersConfiguration.Default(null);
-
-        CreateDummySql(parent, knownFolders[Sprocs]); // make sure there's something that could be logged...
-
-        await using (var migrator = Context.GetMigrator(db, parent, knownFolders))
-        {
-            await migrator.Migrate();
-            Assert.True(await migrator.DbMigrator.Database.VersionTableExists()); // we migrated into the `grate` schema.
-        }
-
-        // Now we'll run again with the same name but different cased schema
-        var grateConfig = Context.GetConfiguration(db, parent, knownFolders) with
-        {
-            SchemaName = "GRATE"
-        };
-
-        await using (var migrator = Context.GetMigrator(grateConfig))
-        {
-            await migrator.Migrate(); // should either reuse the existing schema if a case-insensitive server, or create a new second schema for use if case-sensitive.
-            Assert.True(await migrator.DbMigrator.Database.VersionTableExists()); // we migrated into the `GRATE` schema, which may be the same as 'grate' depending on server settings.
-        }
-    }
 }