I am restoring a database from a SQL Server Enterprise Edition onto a Standard Edition server.  I keep getting an error stating:      Database 'MyDatabase' cannot be started in this edition of SQL Server because part or all of object 'containedmemebersnapshots' is enabled with data compression or vardecimal storage format. Data compression and vardecimal storage format are only supported on SQL Server Enterprise Edition.   As a result, my database is in suspect mode.  Is there any resolution so I can restore this database onto SQL Server Standard Edition?
124234
There is a requirement in our project where they want to evaluate if it is possible to downgrade SQL Server from Enterprise to Standard edition and if a server can be decommissioned.  How can I identify which servers are suitable for downgrade?
49810
I'm using SQL Server Management Studio 2016. When I try to create a local database by right clicking on Databases and selecting "New Database" I get the following error:    I've tried restarting SSMS and the machine.  I can create the database through SQL, however I get the same error when trying to launch any GUI dialogs for the database. So creating it thru SQL doesn't work around my issue as I need to configure it also (and I don't want to write scripts for everything).
102541
When I install SQL Server into the root of my drive, for example D:\, I get an error when I run a database deployer from a third party piece of software.  But when I move my SQL Server instance to D:\SQL\ (move it to a folder within the drive) then installation works perfectly.  My question doesn't regard the database deployer but more into the reason why SQL would have an issue with being installed into the root of a drive. Is this bad practice? Why shouldn't I install SQL Server to the root of my drive?
69435
Help! My master database is corrupt, I can't even bring the SQL instance online! What are my options to get my server back up?   I do have a backup of master, but the  asks me to start the instance in single-user mode, which I can't do!  (Note: I'm leaving this question unspecified as to SQL version, so as to be a more widely-applicable reference. There are some similar questions on DBA.SE, but none that involve the server unable to start.)
32251
Do you use SQL Server Developer Edition on server-class machines in DEV and STAGING environments?  I am working on a large project where (if it passes the proof of concept stage) we will have several large geographically distributed enterprise class database servers running SQL Server 2012 Enterprise Edition.  We will have a production environment will initially have 3 servers, our Staging environment will have a minimum of 3 servers, and our Development environment will have 1 server (hosting three instances).  I was under the impression that we would only need to acquire Enterprise licences for the actual production servers, and we could get by with developer edition in our developer and staging environments because they are not "production".  Other sources have told me that we need to have an enterprise licence on all of the above mentioned machines, and that the developer edition is only meant for a single developer on their workstation.  Since developer edition has all the sexy features of Enterprise, I can't really see the value of it on a workstation class machine, especially for developing and testing the type of high availability system we are building.  If we have to fork out Enterprise licences for a dev server, that will just about kill our proof of concept stage, thus killing the project.  Forcing an enterprise licence on a staging environment will make management just want to skip staging altogether.
58737
I Copied some database backups from one server to another server(new instance no databases are present).I tried restoring using below command   Restore database dbname from disk='g:\e2bak\dbname.bak' with  stats=10   It failed with below error     Directory lookup for the file "G:\MSSQL$s73g\MDF\dbname.mdf" failed   with the operating system error 3(The system cannot find the path   specified.)Msg 3156, Level 16, State 3, Line 1   Also server level default database settings are to store data and log in   G:\MSSQL10_50.SG\MSSQL   I can overcome the error by specfying move option. But my confusion here is  1.Why database .bak file is looking for G:\MSSQL$s73g\MDF\dbname.mdf",this is the path   of dbname database files in production from where we copied the .bak file  2.Also when I restored the database with move option and took a backup in same server,   I was able to restore the Database with below command  Restore database dbname  from disk='G:\e1ebk\dbname.bak' with replace,stats=10   Can you please help me understand why .Bak file location is pointing out to some other directory(which doesn't even exist in our server and existed only on production server) and in second case why this worked without move option.
5174
I'm getting an error whenever I restore a testing database on SQL Server 2005 that was backed up from SQL Server 2008 R2. It seems that I cannot restore from a higher version of sql onto lower version, how can I solve this?     The media family on device is incorrectly formed. SQL server cannot process this media family. RESTORE HEADERONLY is terminating abnormally.   I already tested to restore the same file in its own server (SQL Server 2008 R2) and it works, so it's not corrupted.  I cannot install the updated version of SQL into my older server, so how can I use my older SQL Server 2005 as a dev server but with the updated life data from a different instance?
76944
I have a draft of requirements that look like this:   Production database should be copied in real-time to "Pre-prod" database The Pre-prod database should be available to read and update It should be possible to make schema and data changes to Pre-Prod Schema and data changes on Pre-prod should not effect Prod   The databases will be on the same SQL Server instance.  I'm wondering what approach to take? Transactional Replication seems the best option, but applying schema changes to a subscriber seems like a recipe for disaster.  Mirroring is out because the mirror will not be available; log shipping is out for similar reasons.  Are there any other technologies I should be considering?
109746
We're in the process of a server migration from an on-premise server (Win2008R2) to Azure PaaS.  To move the databases, we used the  tool, which worked great and we can connect to the migrated Azure DB via SQL Server Management Studio.  Considering:    Made quite a few changes to the migrated Azure database (tables, SPs, indexes) to work with the apps in Azure Combined multiple DBs from the on-prem server into one DB in Azure via DMA to save costs  One on-premise database is continually being modified by insert and update operations (multiple tables) during the migration process When fully switching hosting in Azure we need to make sure all data is up-to-date. This will be done very early in the AM during which on-prem IIS websites are stopped assuring no DB operations are made, giving us a short window to migrate missing data   Question: What is the best and fastest way to migrate data (all vs missing/updated) considering the above?  Can this be achieved by following the below steps?   Create a new empty Azure SQL database (to later hold all the tables of 5 on-prem databases) Via , migrate only the schema of that one on-prem database which is continually being modified by insert/update operations Via , set up auto data sync (e.g. every 30 minutes) between the on-prem and Azure database After data sync up and running, via - migrate schema and data of the rest of the on-prem databases (no data changes during migration process) into the single Azure database previously created and used for syncing   EDIT:  After enabling Data Sync in the Azure portal, the sync was unsuccessful due to the below logged errors:   Member Database: MyAzureDb -> Tombstone cleanup failed with the exception "SqlException Error Code: -2146232060 - SqlError Number:18456, Message: Login failed. Member Database: MyAzureDb -> Database provisioning failed with the exception "SqlException Error Code: -2146232060 - SqlError Number:18456, Message: Login failed.   To fix 1 and 2 above tried: ALTER ROLE DataSync_executor ADD MEMBER [myUser]; but got Cannot add the principal 'myUser', because it does not exist or you do not have permission.   Member Database:MyOnPremDb: -> Database provisioning failed with the exception "SqlException Error Code: -2146232060 - SqlError Number:325, Message: Incorrect syntax near 'MERGE'. You may need to set the compatibility level of the current database to a higher value to enable this feature. See help for the SET COMPATIBILITY_LEVEL option of ALTER DATABASE. SqlError Number:156, Message: Incorrect syntax near the keyword 'AS'.    The current compatibility level of the on-premise database is 80. Not sure what impact setting it to 100 will have to the production databse/apps.
32195
I have SQL Server 2012 backup files and want to restore these to SQL Server 2016/2014. Will it work?  I need to find this out before I uninstall SQL Server 2012.
105387
I checked the forum there are other similar topics but my scenario is different. for myDatabase under database properties -> General tab it shows:  Size : 25285.31 MB Space Available: 3989.13 MB   And on disk   myDB.mdf = 10.0 GB (10,745,806,848 bytes) myDB_log.ldf = 14.6 GB (15,767,764,992 bytes)   As per my understanding only 10GB is allowed in Expres edition but here it seems more. What is the space available parameter from DB properties.
73931
I have a Database nearly 1.9Gb Database in size, and MSDE2000 does not allow DBs that exceed 2.0Gb  I need to shrink this DB (and many others like this at various client locations).  I have found and deleted many 100's of 1000's of records which are considered unneeded: these records account for a large percentage of some of the main (largest) tables in the Database. Therefore it's reasonable to assume much space should now be retrievable.  So now I need to shrink the DB to account for the missing records.   I execute DBCC ShrinkDatabase('MyDB')...... No effect. I have tried the various shrink facilities provided in MSSMS.... Still no effect. I have backed up the database and restored it... Still no effect.   Still 1.9Gb  Why?  Whatever procedure I eventually find needs to be replayable on a client machine with access to nothing other than OSql or similar.
13222
I feel that my shop has a hole because we don't have a solid process in place for versioning our database schema changes. We do a lot of backups so we're more or less covered, but it's bad practice to rely on your last line of defense in this way.   Surprisingly, this seems to be a common thread. Many shops I have spoken to ignore this issue because their databases don't change often, and they basically just try to be meticulous.  However, I know how that story goes. It's only a matter of time before things line up just wrong and something goes missing.   Are there any best practices for this? What are some strategies that have worked for you?
35716
Through my frustration of not finding the post-installation wizard with ArcSDE 10.1 and being unsuccessful with the command line tool to start an SDE service on our SDE databases, I found I was able to access the databases and copy/past/add features/delete features/etc. all through direct connections to our SQL Server 2012 machine. This was WITHOUT ArcSDE running.   So... The question is, why do I need to go through the trouble of trying to get the SDE services to run if I can manage our databases through the Desktop tools? I was even able to create an enterprise geodatabase and verified that all of the necessary business tables were created. I have even recreated all our map services in ArcGIS Server 10.1 with direct connect and the web editing is perfectly working.   Perhaps I'm missing something...  UPDATE:  As indicated in the  topic:     "The recommended method to access enterprise geodatabases is to   connect directly from ArcGIS clients. If you only use direct   connections to your geodatabase, you do not have to install the ArcSDE   application server."   If you need to edit settings in the ArcSDE system tables, though, you should still install the command line tools included with the application server. I don't think editing system tables directly through SQL is supported technically.
30126
Currently I deleted one table from the database. But now I want some of the information from that table.   Please suggest how to restore or get back the table.  I am using SQL Server 2008 R2.
72376
Purely a theoretical question as I've been considering possible DR scenarios...  In this scenario:   The link between a principle and a mirror server becomes unavailable for a period of time (e.g. network outage) Incremental log backups are still being taken during this time Then the principle database fails and is unrecoverable   Is it possible to restore the incremental log backups onto the mirror to bring it up to date and back online, or would you need to start from scratch with a restore of a full backup?  Depending on the size of the database the difference could be hours of downtime so it would be nice to know.  I'm predominantly interested in SQL Server 2008 R2 and 2012 but other people may be interested in other versions if there's a difference.
17901
We are going through a downgrade process from SQL Server 2008 R2 Enterprise to Standard edition.  To kick off the above activity, we were looking for available Standard Edition of SQL Server. We found one, but got confused on below points:   The setup files (saved by an earlier team member) are in a folder that says it is SQL Server 2008 R2, but just to cross check before we start installing, we went through the default.ini file, which says:   SQLSERVER2008 Configuration File [SQLSERVER2008]    This created a doubt if this is the correct version of SQL Server required. So is there any other way, in case above mentioned method is incorrect to determine the version, before we actually go ahead and try installing? Can we also check the edition of that available SQL Server, because on the set up, we can hardly figure out if it is really Standard Edition?   We cannot simply download new media, per our security policies. Also, we have no rights to download.