Backup Encryption in SQL Server Standard Edition

Hello,
I need experts advice on Backup encryption options available in SQL Server 2008 R2 Standard Edition. I know TDE is available, but only in Sql Server 2008 R2 Enterprise edition. But we are using Standard Edition.
Thanks

Password protect is not the same thing as encryption - the data is still clear text. This is what Books Online for SQL Server 2008 say about the password option:
"The protection provided by this password is weak. It is intended to prevent an incorrect restore using SQL Server tools by authorized or unauthorized users. It does not prevent the reading of the backup data by another method or the replacement of the password.
This feature will be removed in the next version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature. "
And in 2012 this option is indeed removed from the backup command.
Tibor Karaszi, SQL Server MVP |
web | blog

Similar Messages

Using BizTalk Enterprise Edition 2009/2013 with SQL Server Standard Edition vs Enterprise Edition

Hi All,
I would like to know what are the Drawbacks of using BizTalk Server Enterprise Edition 2009/2013 with SQL Server Standard Edition vs Enterprise Edition.
We are currently using Enterprise Edition.
1) Are there any adverse performance constraints? Microsoft mentions to use SQL Server Enterprise Edition for "Optimal Performance" but does not expand on the topic.
2) Any features missing?
2) Is there a supported way to downgrade SQL Enterprise to Standard for an exisiting BTS Environment?
Thanks!

1) SQL Standard is limited to 4 CPU's and 64GB of memory while Enterprise is 8 CPU and 2TB or memory.
2) The only BizTalk feature dependency on a SQL Enterprise feature is BAM Real-Time Aggrigations which requires Analysis Services RTA.
3) Yes, but it's not a SQL downgrade really, you would move the BizTalk databases:
http://msdn.microsoft.com/en-us/library/aa559835.aspx

Can we use SSRS in sharepoint 2013 standard and sql server standard edition

can we use SSRS in sharepoint 2013 standard and sql server standard edition
MCTS Sharepoint 2010, MCAD dotnet, MCPDEA, SharePoint Lead

Yes you can. You do lose some features:
http://msdn.microsoft.com/en-us/library/cc645993.aspx#Reporting
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

SQL Server Standard Edition with Sharepoint 2013 Enterprise

Hi there,
I need some help figuring out what will be the ideal SQL Server Standard Edition that can run all features for SharePoint 2013 Enterprise Edition. I ordered CAL licenses for a Sharepoint 2013 Enterprise Server (Supports 500 users). Now I need to find out
if it is worth upgrading SQL server to the following:
Upgrade to SQL Server Standard R2 2012 or upgrade to SQL Server Standard 2014? Basically, I am looking for the pros and cons?
-Esteban
Microsoft manager to programmer: You start coding. I'll go find out what they want ...

Hello,
PowerPivot for SharePoint is a feature available only if SQL Server Enterprise Edition and Business Intelligence Edition is used. Reporting Services of SQL Server Standard has also some limitations that will impact SharePoint 2013.
Additionally, SQL Server Standard Edition do not offer AlwaysON, database snapshots and online index rebuild.
To me, the biggest difference between SQL Server 2012 Standard Edition and SQL Server 2014 Standard Edition is that SQL 2014 Standard now supports 128 GB of RAM. SQL Server 2012 Standard is limited to 64 GB.
https://msdn.microsoft.com/en-us/library/cc645993.aspx#CrossBoxScale
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Downgrade SQL Server Enterprise Edition to Standard Edition

Hi
I came to know in-place edition downgarde from SQL Server Enterprise to SQL Server Standard edition is not possible after seeing couple of questions in the forum, But I find one interesting article in the web which says in-place downgrade is possible and
I tried the same and it works for me, below are the steps
1.    Type regedit.msc
2.    Got to SQL installation section in registry by default it will be here:
HKLM(HKEY_LOCAL_MACHINE) -> SOFTWARE -> Microsoft -> Microsoft SQL Server ->
3.    Here you have to select the instance you want to downgrade if you have multiple instances.
Expand required instance folder.
MSSQL10_50.MSSQLServer -> Setup
4.    Click on ‘Setup’
5.    Here You need to change one by one all below entries.
AGTGroup
DigitalProductID
Edition
EditionType
ProductCode
ProductID
SQLGroup
FDHostGroup
Checksum
Take these values from any already installed Standard edition instance and replace here.
Make sure from where you are taking these values have the same features installed and same version and all.
6.    Now click on ‘SQL_Engine_Core_Inst’ and change the entries here as well.
         ProductCode
But I am not sure how reliable is that option, Could someone let me know can I use that process for downgrade
Regards
calyan
Kalyan Akula

Hi,
I would ceratinly not do that If I were you, this would surely leave you in unsupported state. You should ask Microsoft whether tweaking registry and replacing just value can actually change enterprise to standard or whether it is supported or not. I guess
you are just fooling the system.
Its better to uninstall Enterprise edition and Install Standard edition and create database using backup restore or attch detach.
I have not tried what you have mentioned. But thank you for the information.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Downgrade SQL Server 2008 Enterprise to SQL Server2008 Standard Edition

I would like to know from fourm users, what are the necessary steps I would take care for above mentioned activity and also please let me know best suitable option for Production.
SNS

You can't do in-place downgrade. You need to go with backup -> uninstall ent -> install std -> bring it to same patch -> restore databases approach.
You need to make sure that there is not enterprise only feature used else you can't restore database on standard.
Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
Balmukund's answer above is the Microsoft supported route for doing a downgrade of an instance of SQL Server. However, before you do this, you need to query the sys.dm_db_persisted_sku_fearures DMV in each of your user databases to make certain that
you don't have any Enterprise features in use that would block your ability to restore a database onto Standard Edition.
No matter what you are going to have to do an uninstall and reinstall of the SQL Server instance to downgrade the SKU. However, you can save yourself some time and the headache of trying to restore the system databases if you are careful about what
you do. I have done a couple of SKU downgrades in the past and the easiest way to do it, and I am not saying this is the Microsoft supported way but that it works if done correctly, is to:
Take a good backup of all of your databases (system and user).
Run SELECT @@VERSION and note the specific build number of SQL Server that you are currently on.
Shut down your existing instance of SQL Server.
Copy the master, model, and msdb database files (both mdf and ldf), don't move them copy them, from the current location to a new folder that you mark as readonly.
Uninstall SQL Server from the system.
Reboot the server.
Install SQL Server Standard Edition.
Apply the necessary Service Pack and/or Cumulative Updates to bring the instance up to your previous build number.
Shutdown SQL Server.
Copy the master, model, and msdb database files (both mdf and ldf) from the folder you saved them in to the correct location for the new install and remove the readonly flag from the files, and change the file ACL's so that the SQL Service account has Full
Control over the files.
Startup SQL Server and if you did it correctly it will startup and be exactly where you were before you made any changes, with all of your user databaes online and you should be ready to let applications connect and resume operations.
If you screw something up in the above, you still have your backups and you can run setup to rebuild the system databases and then go about following the Microsoft supported path for restoring the system databases and then user databases into the system
to bring it online. Essentially the file copy is no different that what would occur through attach/detach you are just doing it with system databases which is not supported, but it does work. The key is to have your backups from before you do anything
so you have the supported route available if you encounter an issue. The only issue I have ever had doing this set of steps is that I didn't set the file ACL's correctly and the database engine threw Access Denied errors and failed to start until I fixed
the ACL's correctly. This can save you many hours of frustration and downtime trying to restore everything since the database files are already there and it is just some small copy operations to put them where you need them to be.
Balmukund, feel free to beat me over the head for suggesting a non-supported path. :-)
Jonathan Kehayias | Senior Consultant,
SQLSkills.com
SQL Server MVP | Microsoft Certified Master: SQL Server 2008
Feel free to contact me through
My Blog or
Twitter. Become a
SQLskills Insider!
Please click the Mark as Answer button if a post solves your problem!

SQL Server 2012 Edition required for my case??

Hi,
I am setting up a SharePoint 2013 BI environment with minimal servers. Below is the configuration:
1) WFE1 - Front End Server Role
2) APP1 - Application Server Role with SSRS 2012, SSAS in SharePoint mode.
SQL Server 2012 BI edition is used here for SSRS and SSAS in SharePoint mode
3) DB Server - SharePoint content databases only
- Can this SQL Server be standard edition ? or does this server also need to have minimum BI features which means it should be BI or Enterprise edition?
Thanks
Sandeep
Sandeep Nakarmi www.snakarmi.me

Hi Sandeep,
Thanks for posting your query, Below are the URLs that describe the situation to USE the SQL SERVER Standard or Enterprise Edition for BI features. Kindly go through these URLs once to get the difference.
http://searchsqlserver.techtarget.com/feature/When-to-consider-SQL-Server-Enterprise-Edition
http://searchsqlserver.techtarget.com/feature/SQL-Server-Standard-Edition-Why-its-worth-the-cost
Of course, you will get more features for BI in as sequence SQL Server Edition mentioned below
Express < Standard < Enterprise
Moreover, browse the below mentioned URL to enable BI features in SharePoint
http://blogs.technet.com/b/ldusolier/archive/2014/05/19/use-of-bi-capabilities-in-sharepoint-2013-with-sql-server-2012.aspx
I hope this is helpful to you, mark it as Helpful.
If this works, Please mark it as Answered.
Regards,
Dharmendra Singh (MCPD-EA | MCTS)
Blog : http://sharepoint-community.net/profile/DharmendraSingh

To configure SSIS packages out of these SQL Server Standard, Web and Workgroup editions which is preferred?

Hi All,
To configure SSIS packages out of these SQL Server Standard, Web and Workgroup editions which is preferred?
Grateful to your time and support. Regards, Shiva

Hi Shiva,
SSIS designer and runtime, basic transforms, and data profiling tools are only supported by Standard and higher editions. Besides, some advanced SSIS adapters such as High performance Oracle/Teradata destination and Dimension processing destination adapter
are only supported in Enterprise edition. So, if you need to develop/modify SSIS packages on this server, Standard or even Enterprise editor is recommended.
Reference:
http://msdn.microsoft.com/en-us/library/cc645993.aspx#SSIS
Regards,
Mike Yin
TechNet Community Support

Install MS SQL Server Web Edition on a server with MS SQL Server Express

Hi,
We have a VPS cloud server on which there is an instance of SQL Server Express.
Since we need more resources, I consulted with the hosting provider and they offered us to use SQL Server Web Edition (SPLA Lisence).
My question is - the hosting company claims that it is not possible to keep the SQL Server Express instance along side with the SQL Server Web Edition, and that we must do ugrade and remove the SQL Server Express instance.
This will cause us a long downtime, since there are multiple DBs on the SQL Server Express that we will have to backup, and then restore them one by one on the Web Edition after it is installed.
Is this correct? Can't we install the SQL Server Web Edition Instance and gradually move the DBs to it?
Thanks!

The 50 instances per machine is a setup check rule as opposed to a hardware limitation. From this perspective, there would be no difference between a VM or a physical server.
In the line from the documentation that you referenced, the "stand-alone server" refers not to VM vs. Physical, but instead a stand-alone instance vs. a clustered instance. That is, in a non-clustered environment, you can have up to 50 instances.
In the past when I helped with setup testing and automation, we'd run VMs with 20-ish instances, including instances from 2012, 2008 R2, 2008, and 2005, including multiple editions (Enterprise, Standard, Express, Web, etc.).
One other potential option if your provider cannot support multiple instances is to do an in-place upgrade (edition upgrade) of your existing Express instance. This would retain the current instance and upgrade the existing instance from Express
to Web without the need to migrate databases. Here is more info on the supported version and edition upgrade paths (including Express to Web):
http://technet.microsoft.com/en-us/library/ms143393.aspx
Thanks,
Sam Lester (MSFT)
http://blogs.msdn.com/b/samlester
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
"Mark as Answer" and
"Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

Sql Server Web Edition Reporting Services errors when trying to connect to Windows Azure SQL

I am using a preconfigured image from the Azure VM Gallery to create a VM.
--> Sql Server 2012 SP1 Web running under Windows Server 2008 R2
After configuring Reporting Services I get the following error when trying to run a report that connects to my Azure SQL db.
An error has occurred during report processing. (rsProcessingAborted)
An attempt has been made to use a data extension 'SQLAZURE' that is either not registered for this report server or is not supported in this edition of Reporting Services. (rsDataExtensionNotFound)
On the VM using SSMS I can connect to the Azure SQL db. On the VM in Report Builder when I define a connection I get a similar error to the one above when I test that connection. I am using Microsoft Azure SQL as the data source type.
Interestingly in Report Builder, if I proceed past the connection definition, I can see the tables from my Azure SQL db in the dataset definition page.
One more note. If I use a different image from the Gallery (Sql Server 2012 Standard SP1 on Windows Server 2012) my report builder connection works and the reports run fine. I believe that the Azure documentation says that Sql Server Web edition
is an acceptable choice for the SSRS on VM for reporting.
Any thoughts or suggestions?
Thanks -- Tom Reilly

Hello,
A VM with SQL Server 2008 R2 or 2012 supports all Reporting Services features, including all supported data sources, customization and extensibility, and scheduled report execution and delivery.
Did you run the report in Report Manager,or preview the report in Report Builder? Which version of the Report Builder you installed in the Windows Azure VM? SQL Reporting does not support reports created from Report Builder 1.0 or 2.0. You can create reports
using Report Builder 3.0 and then upload the reports.
What's more, please also check the database source credential of the report.
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

Daily backup on Ms sql server management studio (MS sql 2005).

I wander how to perform daily backup on Ms sql server management studio (MS sql 2005).
In sql server Entereprise manager (MS sql 2000) I had no problem to shedule.
But now I do not find this option

Hi
Please follow these steps in SQL Server Management Studio in SQL Server 2005 and <b>award points</b>
1. Start SQL Server Management Studio.
2. In the Connect to Server dialog box, click the appropriate values in the Server type list, in the Server name list, and in the Authentication list.
3. Click Connect.
4. In Object Explorer, expand Databases.
5. Right-click the database that you want to back up, click Tasks, and then click Back Up.
6. In the Back Up Database - DatabaseName dialog box, type the name of the backup set in the Name box, and then click Add under Destination.
7. In the Select Backup Destination dialog box, type a path and a file name in the Destinations on disk box, and then click OK.
8. In the Script list, click Script Action to Job.
9. In the New Job dialog box, click Steps under Select a page, and then click Edit if you want to change the job parameters.
Note In the Job Step Properties - 1 dialog box, you can see the backup command.
10. Under Select a page, click Schedules, and then click New.
11. In the New Job Schedule dialog box, type the job name in the Name box, specify the job schedule, and then click OK.
Note If you want to configure alerts or notifications, you can click Alerts or Notifications under Select a page.
12. Click OK two times.
You receive the following message:
The backup of database 'DatabaseName' completed successfully.
Note To verify the backup job, expand SQL Server Agent, and then expand Jobs. When you do this, the SQL Server Agent service must be running.

Sql 2005 standard edition for sql and AS databases with bpc 7.0 sp3 ?

hello
Install guide tells that we must use SQL 2005 Enterprise Edition with BPC except for Reporting Services.
Customer asks wether he could use SQL 2005 Standard Edition for SQL database and Analysis Services ?
Thanks.

Hello Sorin. Two more questions, please:
1) what do you mean by "Also into Application server you need EE because only in this version you have control flow." ?
Is "control flow" "business process flow" new functionality ?
2) On the other hand, I don't think that BPC admin task is able to handle lite or full optimize without an Enterprise Edition Client.
But customer asks wether it is possible to install on application server
- SSIS standard edition for SSIS service
- SSRS standard edition for Reporting Services
- SQL client Enterprise Edition to let BPC admin task handle lite and full optimize properly.
Why all this ? Because Enterprise Edition costs ten times more than Standard Edition and in a multi-server configuration, customer has to buy several SQL Server licenses, one per server running at least one SQL server service. (For example, with SQL,SSIS and OLAP on one server, and SSIS and SSRS running on the application server, customer has to buy two SQL servers licenses).
Thanks. R.

Speed of SQL server web edition is slow then express edition

Hello,
I have query regarding performance difference between SQL server express edition and web edition.
There two server with same configuration (8 GB Ram, 4 core, hard disk has about 90 GB free memory), both server has only SQL server not any other software or programs which affect the performance.
Software version as below:
Server1: Windows server 2012 R2 & Microsoft SQL Server 2014 - 12.0.2430.0 (X64) web edition
Server2: Windows server 2008 R2 & Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000. 0 (X64) express edition
I have restore one database backup on both servers (So on both server database with same records) and executed some queries on both the servers, Result bit surprising because express edition is always faster than web edition.
Then I have do following things but still result is same:
Rebuild indexes
Make max memory allocation same
Please provide me suggestion to improve speed of Microsoft SQL Server 2014 - 12.0.2430.0 (X64) web edition
Thank in advance.

So exactly the same plan for both. What does Profiler say? Same amount of I/O, CPU? If so, next step would be to eliminate the network and other paths out from the machine. If it is a SELECT, then you can add INTO into a temp table and see if you get the
same performance. If so, you know the issue is with the data leaving your SQL Server ang getting to the client - those aspects.
Tibor Karaszi, SQL Server MVP |
web | blog

SQL Server Express Edition or LocalDb

Can I have free access to SQL Server Express Edition or LocalDb with General Purpose Basic Tier and Standard Tier?
Regards,
Vivekanand

Hi Vivekanand,
Thanks for posting here.
Have a glance at this document hope you get the detailed information.
http://azure.microsoft.com/en-us/documentation/articles/data-management-azure-sql-database-and-sql-server-iaas/
Girish Prajwal

RBS Licensing on a SQL Server Standard 2012 Failover Cluster

I am planning to implement a Sharepoint 2013 installation which is primarily to be used for Document Storage. We are considering using Sharepoint RBS with Filestream with SQL 2012 Standard and as far as I can see on our non-production environments this works
without any issue - i.e. we enable filestream and RBS with Sharepoint and SQL and everything works as expected on our non production systems. In non production we have single SQL Server nodes.
However, in production we have planned to have a 2 node SQL 2012 Standard failover cluster.
On this page, it indicates
"To run RBS on a remote server, you must be running SQL Server 2008 R2 Enterprise on the server that is running SQL Server where the
metadata is stored in the database."
My question is : Am I entitled to use RBS with Filestream on a SQL 2012 Standard Failover Cluster, or is SQL Enterprise required.
If enterprise is required, we will have to remove the RBS. I have reviewed the links below, but cannot see a definitive answer from a licensing perspective
http://social.technet.microsoft.com/Forums/en-US/76e86936-b7ee-4571-aa02-f45b80867515/which-edition-for-sql-server-2008-r2-with-sharepoint-2010-no-foundation?forum=sharepointadminprevious
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2b04979f-c619-48a4-b0e4-3add00345fb0/sql-server-2008-edition-comparisons-in-terms-of-high-availability-rbs?forum=sqldisasterrecovery

Hi antrimcoaster,
Indeed, in Microsoft official document, all SQL editions (Express, Standard, Enterprise…) of SQL Server 2008 and SQL Server 2008R2 support RBS (Remote Blob Store), however, as your post, if you run RBS on a remote server, we recommend you use Enterprise
version especially you want to deploy Remote BLOB Storage with SQL Server 2012 in Production environment. Usually, Enterprise edition is more for mirroring, supporting more RAM/CPU, and custom RBS providers and multiple nodes cluster.
If you had setup and configured RBS successfully with SQL Server 2012 standard, and now you need to want to upgrade to SQL Server 2012 Enterprise, I recommend you reconfigure your blob store, you can review the following similar article.
https://community.dynamics.com/ax/b/axdilip/archive/2012/10/22/configuring-and-implementing-sharepoint-2010-rbs-remote-blob-storage-with-sql-server-2012-part-1.aspx
In addition, for more detailed information regarding to the license issue, please call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please
use the Guide to Worldwide Microsoft Licensing Sites to find contact information in your locations.
Thanks,
Sofiya Li
If you have any feedback on our support, please click
here.
Sofiya Li
TechNet Community Support

Backup Encryption in SQL Server Standard Edition

Similar Messages

Maybe you are looking for