Okay, this is strange.
I installed Windows 8 and SQL Server 2008. The database I am working with has FileStream enabled and so I need to enable FileStream. And so, I did:
EXEC sp_configure filestream_access_level, 2
RECONFIGURE
It didn't work.
So I tried using the UI in SQL Server Management Studio. Like this:
Notice under configured value it is displaying "full access"
And under "running values":
And notice under "running values" it is displaying "disabled".
So I did:
Ran RECONFIGURE, it returns Command(s) completed successfully. Didn't work.
Restart SQL Server 2008. Didn't work.
Restart machine. Didn't work as well.
Now I wonder if I RECONFIGURE is broken or my UI is broken. So I tried changing Default Language to UK - English and ran RECONFIGURE. It worked! The language changed to UK under "running values".
So I guess the problem is Filestream access changes didn't get applied. But why?
I am running Windows 8 64 bit and this version of SQL Server:
Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (X64) Jul 9 2008 14:17:44
Copyright (c) 1988-2008 Microsoft Corporation Enterprise Edition (64-bit)
on Windows NT 6.2 <X64> (Build 9200: )
filestream access level Server Configuration Option:
Before this option has any effect, the Windows administration settings for FILESTREAM must be enabled. You can enable these settings when you install SQL Server or by using SQL Server Configuration Manager.
Related
I'm trying to attach a SQL Server .mdf to my Management Studio 2014, but I get the error:
Attach database failed for Server '...\SQLINSTANCE'. (Microsoft.SqlServer.Smo)
Additional information:
An exception occured while executing a Transact-SQL statement or batch.
(Microfost.SqlServer.ConnectionInfo)
The database 'DatabaseName' cannot be opened because it is version 706. This server supports version 663 or earlier. A downgrade path is not supported.
Could not open new database 'DatabaseName'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 948)
The .mdf was created on SQL Server 2012 (which presumably is represented as 'version 706' in the error message).
OK, so I need to upgrade my DB engine to 2012 on my home PC. That means installing 2012 Express from https://www.microsoft.com/en-gb/download/details.aspx?id=29062
A couple of questions though before I do that. By installing 2012, would it be added to Management Studio 2014 automatically? Would I then have both 2008 & 2012 as options for new databases I might want to create, or would 2012 simply replace 2008?
On the download page, it says the supported OSs are "Windows 7, Windows Server 2008 R2, Windows Server 2008 Service Pack 2, Windows Vista Service Pack 2". But I'm using Windows 10. Is this just a case of MS not updating the page or does 2012 really have a problem with Windows 10?
EDIT: It's true that this question is similar to ones previously asked on SO (such as The database cannot be opened because it is version 706), but here I'm not contemplating rolling back the 2012 version of the DB to 2008, but issues pertaining to installing 2012 on my home PC.
So, your SQL Server version is 2008 - you have 2014 management studio and you need to use a database from a server version 2012.
If that is the case; then I hope some of the following will help:
Windows 10 can run SQL Server 2012 fine.
The documentation might just not be updated, but I've not personally seen any issues on multiple instances.
Management Studio 2014 can connect to SQL Server version 2012 as well. You don't need to install it again.
Unless you wish to remove SQL Server 2008, you'll need to install 2012 as a new instance, so you basically have two SQL Servers running. This however, will have affect on how you connect to the databases.
Check out, for example: https://msdn.microsoft.com/en-us/library/ms143531.aspx for more information
So instead of having multiple instances, consider whether you'll still need 2008, so it might be removed if you don't need it at all.
Also - consider whether it might be worth it to upgrade your local instance to newer version - 2014 for example. However this of course might give you the same problem in reverse in the future, if you ever need to make a database on 2014 instance and move it to a 2012 instance.
It all depends on the actual requirements, set-up and development models. Basically because you say it's your home computer, I'd think the newest version might just be the best approach, as you're less likely to use that version as a "creator" rather than a development version.
I/m trying to replicate a database whose .bak was created using SQL server 2008 R2, as in my local machine I was running SQL server 2008 I'm trying to upgrade.
It does the upgrade and the management studio shows the actual R2 version but the running instance is not changing, i.e. the Sql Server in the connection stills stays 10.0.1600
I uninstall everyting and run first 2008 and then the update, so I'm pretty sure it is the default instance and not a named one. And I couldn't install directly 2008 R2 because I was running through all kind of problems and that's why I'm trying to install 2008 first and then update
Anyone know if I can change that MSSQLSERVER version to the proper one?
Thanks
Update
When running select##version as per Giorgi's comment I get this
Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (X64) Jul 9 2008 14:17:44 Copyright (c) 1988-2008 Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
I have an application written in MS ACCESS 2007 using VBA, connecting to an SQL Server at the back end. Both Access and SQL Server are running locally.
My machine runs Access 2010 and MS SQL Server Express 2008 R2 (both 32-bit, on WinXP) with no problem.
I have another machine, Win7 64-bit, running both Access 2010 and SQL Server 2008 (NOT R2) 64-bit.
When I run the Access application on the 64-bit machine, I have a drop down box to select the SQL Server which holds the various databases. When I select the server, after a few seconds I get an error:
Run-time error '-2147024703 (800700c1)':
Automation error %1 is not a valid Win32 application.
When I select the Debug option, the yellow arrow points to:
Set oServer = New SQLDMO.SQLServer
The next line is:
oServer.Connect ServerName, strSQLUser, strSQLPwd
In the watch list, I can see that ServerName, strSQLUser, and strSQLPwd hold the right values to access the SQL Server. I've tested these in sqlcmd and successfully was able to query tables.
Can anyone please help me out on this one? I'm not sure what to do next.
Seems like you've got registered a 32-bit SQLDMO on your system that is being used for connection to the 64-bit instance. Check your registry / file system for SQLDMO.dll versions and register the correct one.
Also check MSDN "Installing SQL-DMO" because SQLDMO was scheduled for remove after SQL Server 2008 R2:
Avoid using this feature in new development work, and plan to modify applications that currently use this feature.
SQL Server Database Management Objects (SQL-DMO) has been removed from SQL Server 2008 R2 Express and the SQL Server 2008 R2 Feature Pack. SQL-DMO also does not support Database Engine features introduced after SQL Server 2000. We recommend that you modify applications that currently use this feature as soon as possible. If you must support SQL-DMO, install the Backward Compatibility Components from the SQL Server 2008 Feature Pack from the Microsoft Download Center. Do not use SQL-DMO in new development work; use SQL Server Management Objects (SMO) instead. You can obtain the SMO documentation by installing SQL Server 2008 R2 Books Online.
Thanks for this.
I looked to find SQLDMO.DLL 64-bit version, but although using the Backwards Comparability package for x64, installing using the MSI did not do the job.
I had to manually extract the files and place the correct version (which is ~2MB larger than the x86 version as an indication to knowing which one is the x64) and then run 'regsvr32 sqldmo.dll ' in the command line (very important: need to run cmd as Administrator for this to succeed).
After the module has been registered, my Access front end run great.
I have installed Windows Server 2008R2x64 under VMWare Workstation, to test installation of my application. I then installed the .Net 4.0 distributables and then SQL Server Express 2008 R2 SP1 (SQLEXPRWT_x64_ENU.exe from http://www.microsoft.com/download/en/details.aspx?id=22973). I accepted all defaults and including the default instance SQLExpress.
When I can start the management console, SQLEXpress is not available as an instance.
In Administrative Tools > Services, SQL Server is running, with instance SQLServer. I have enabled the Agent and Browser services.
This is killing me as I need to install at a customer site on Monday...
Any ideas?
Seems like all that was required was a restart. After that I was able to browse to the instance...
I've got a client that I wrote an asp front end application 2 yrs ago, which connects to a access 2007 database. All the files sat on a windows server 2000 machine 2 yrs ago. They recently upgraded their server to a windows server 2008 machine (64bit). Now the asp can't connect to the Access database via the ODBC connection. I tried using a dsnless connection, as well as, a manually created dsn connection (the manual dsn was created on the server 2008 machine using the 32bit .exe wizard to create dsn connections)...but that didn't work. I get an error that basically says the database odbc couldn't connect.
I've read that this is a problem between a 64bit 2008 server and a 32bit application (access 2007), but I can't seem to find any solutions to fix this problem.
Can anyone point me in the right direction, or offer some help? I'm really clueless how to solve this for them and they really don't have any other people to help.
Thanks for your help.
On a Windows 2008 x64 the following can be done to enable 32 bit applications in IIS:
Open IIS (inetmgr command)
Locate the application pool that your application is using
In the pool's advanced settings, set Enable 32-bit Applications to true
If that doesn't work, try enabling 32 bit compatibility mode by using the following command:
cscript c:\inetpub\adminscripts\adsutil.vbs SET /w3svc/AppPools/Enable32BitAppOnWin64 True
Hope it helps!