We have two IaaS VMs in Azure and a CREATE DATABASE statement takes 3 seconds in one and 72 seconds or even longer, on the other. (SQL 2014)Both same VM configs, only differences is SQL Standard vs Enterprise.However, to my knowledge, that should not have any impact on CREATE DATABASE nor on instant file init.Instant File Initialization is enabled for both and I verified by using trace flag and checking SQL log to see that log file was zero'd but database was not:MessageZeroing completed on F:\SQLData\DummyTestDB_log.ldf --Log YES, database file, not mentioned and therefor not.Here is database create statement:[code="sql"]CREATE DATABASE [test]CONTAINMENT = NONEON PRIMARY ( NAME = N'test', FILENAME = N'F:\SQLDATA\test.mdf' , SIZE = 262144KB , FILEGROWTH = 1024KB )LOG ON ( NAME = N'test_log', FILENAME = N'H:\SQLDATA\test_log.ldf' , SIZE = 128000KB , FILEGROWTH = 10%)[/[/code]So at this point I am at a loss.Other than disk I/O issues.Anything else on the SQL server config side that I should be looking at?Thanks!
↧
