Archive for the ‘ Databases ’ Category
While editing documents in RavenDB Management Studio for testing, it became evident that the changes were not reflected in the website that was using the database. By default, RavenDB caches client queries. This article describes how to disable this feature, should the need arise.
Named pipe support is apparently broken in PHP 5.3.x on Windows. When upgrading from PHP 5.2.x or earlier the following error message may appear in the PHP error log:
PHP Warning: mysql_connect() [<a href='function.mysql-connect'>
function.mysql-connect</a>]: php_network_getaddresses:
getaddrinfo failed: No such host is known.
The recommended way to create SQL databases from Entity Framework models is to use a dedicated database server. However, in some instances you may want to create the database in a .mdf file inside the application’s App_Data directory. While this is definitely possible, the solution is certainly not straightforward and not entirely possible from within Visual Studio alone. One needs to connect to an existing SQL Server database instance in SQL Server Management Studio and manually attach the .mdf database file to that instance.
When installing SQL Server Management Studio on top of an existing SQL Server 2008 or SQL Server 2008 R2 installation, the setup program may fail with the following .NET Framework exception, even if the .NET Framework 3.5 and 4.0 is already installed on the target machine:
System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings: Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified. (C:\Documents and Settings\[UserAccountName]\Local Settings\Application Data\Microsoft_Corporation\LandingPage.exe_StrongName_ryspccglaxmt4nhllj5z3thycltsvyyx\10.0.0.0\user.config line 5) ---> System.IO.FileNotFoundException: Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified. File name: 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' at System.Configuration.TypeUtil.GetTypeWithReflectionPermission(IInternalConfigHost host, String typeString, Boolean throwOnError) at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.Init(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord) at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.InitWithRestrictedPermissions(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord) at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory..ctor(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord) at System.Configuration.RuntimeConfigurationRecord.CreateSectionFactory(FactoryRecord factoryRecord) at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)
Current versions of MySQL 5.1.x appear to ship with an outdated default configuration file that generates the following warning in the Windows Event Log upon restarting the MySQL service: The syntax ‘–default-character-set’ is deprecated and will be removed in a future release. Please use –character-set-server instead.
This article is part of a backup. It was originally posted on Sunday, April 13. 2008.
At the very bottom of the SQL Server 2005 Express download page, Microsoft offers 64-bit versions of their installers. Unfortunately, this is not everything you need to run SQL Server Express on 64-bit versions of Windows Vista. As it turns out, the installer currently provided on the download page is bundled with the 32-bit version of the SQL Server Native Client, which causes the subsequent SQL Server installation to fail with the following symptoms:
Restarting the whole installation or uninstalling the Native Client doesn’t help.
This article is part of a backup. It was originally posted on Sunday, April 13. 2008.
The MySQL Server Instance Configuration Wizzard MySQLInstanceConfig.exe (current version 1.0.10.0) that comes with the MySQL Server Community Edition (current version 5.0.51a) has a typo in the embedded manifest file that prevents it from running on Windows Vista machines.