We are migrating SSRS from a work group server to a domain server. Is there a way to migrate all users from the existing server to the domain server? We have 300 windows users on the existing server. SQL 2008 R2 version.
I think Active Directory Migration Tool should help you with the task. Here are details on where to get tool from. Microsoft also provides a documentation/manual. There is also a discussion on a similar topic on SQL Server Forum if you need further guidance.
Related
Is it possible to create link server in SQL Server 2008 for Teradata using Windows authentication? Couldn't find any information about that. All examples in google use already specified user for connect.
Thanks.
I recently did a backup/restore of some catalogs from one server to another. Both servers are still up. User access to the servers is controlled via Active Directory and server roles. On the old server, there is no issue with continued user access. On the new server, however, we get log on errors. As near as I can tell (I may not have total access), the group set-up are the same on both servers. Where can I look for differences?
Databases: SQL Server 2012 11.0.3000
OS: Windows Server 2008 R2 Enterprise SP 1
Testing: access was tested through Access (used only for the UI) and Excel connecting to SQL Server.
User accounts: Access is done through a domain lookup, not a local account.
My hope for an answer is some direction in investigation. I am not a DBA. support process is moving too slow. It is a production issue so I am hoping to get a resolution quickly.
Michael
What I found out was that the ad group must be in both the server security group as well as the catalog security. for the affected ad group, it was only in the catalog security group, not the server. thanks.
I am trying to create a .bacpac file of my SQL 2012 database.
In SSMS 2012 I right click my database, go to Tasks, and select Export Data-tier Application. Then I click Next, and it gives me this error:
Error SQL71564: Element Login: [myusername] has an unsupported property IsMappedToWindowsLogin set and is not supported when used as part of a data package.
(Microsoft.SqlServer.Dac)
I am trying to follow this tutorial so that I can put my database on Azure's cloud:
http://blogs.msdn.com/b/brunoterkaly/archive/2013/09/26/how-to-export-an-on-premises-sql-server-database-to-windows-azure-storage.aspx
How can I export a .bacpac file of my database?
SQL Azure doesn't support windows authentication so I guess you'll need to make sure your database users are mapped to SQL Server Authentication logins instead.
I found this post referenced below which seems to answer my question. I wonder if the is a way to do this without having to delete my user from my local database...
"... there are some features in on premise SQL Server which are not
supported in SQL Azure. You will need to modify your database before
extracting. This article and several others list some of the
unsupported features.
This blog post explains how you can use SQL Server Data Tools to
modify your database to make it Azure compliant.
It sounds like you added clustered indices. Based on the message
above, it appears you still need to address TextInRowSize and
IsMappedToWindowsLogin."
Ref. http://social.msdn.microsoft.com/Forums/fr-FR/e82ac8ab-3386-4694-9577-b99956217780/aspnetdb-migration-error?forum=ssdsgetstarted
Edit (2018-08-23): Since the existing answer is from 2014, I figured I'd serve it a fresh update... Microsoft now offers the DMA (Data Migration Assistant) to migrate SQL Server databases to Azure SQL.
You can learn more and download the free tool here: https://learn.microsoft.com/en-us/azure/sql-database/sql-database-migrate-your-sql-server-database
As of 9/2018, there is a new tool called the Data Migration Assistant that can help with the task of migrating an existing on-premise SQL Server Database to Azure. While the tool will NOT resolve the issue of migrating Windows Logins, it will at least help you get your database schema and data migrated up to Azure.
Here is the overview of the tool: https://learn.microsoft.com/en-us/sql/dma/dma-overview?view=sql-server-2017
You can download the Data Migration Assistant here:
https://www.microsoft.com/en-us/download/details.aspx?id=53595
Once you have migrated your database up to Azure, you can configure an AD Administrator on the SQL Server, then create contained users in your database to allow users to login to your SQL Database with their Windows accounts.
I am setting up SharePoint 2010 on one machine with SQL Server on a separate box to server as both the data store and serve reporting services (through SSRS/SP Integration).
In the past, I would install the WSS 3.0 for SharePoint 2007 on the SQL Server Box. It appears that there is no existing option for SP 2010. Am I missing something? Thanks.
It is possible, I believe you can specify a Database server when you are configuring the product.
This is probably a good start: http://technet.microsoft.com/en-us/library/ee667264.aspx
There are a number of "buried" articles ( for some reason I couldn't google them) in the Microsoft Sharpoint Documentation Tree:
(since I could not pust multiple links youre stick with this one)
Configuring on Multiple servers - my specific case
I am going to use SSRS to generate report for my website.
Scenario:
I have 2 servers, Application server & Database Server.
I want to have reports(.rdl files) sitting on Application server(IIS) accessing data on SQL server(Database Server)
In order to fulfil these requirement I require to install SQL server 2k5 on my Application server just for having SQL server reporting service. So I am just waisting one of licence of SQL server by installing that on Application server.
Is anyone having any idea how to install only reporting service with SQL server 2k5??
In order to have Reporting Services on your Application server, you would have to use a SQL license. You can install just the Reporting Services section of SQL Server, but it is still technically part of the SQL Server application and requires a license for use on that processor(s).If that is a huge issue, then I would have to recommend keeping the Reporting Services section installed with the rest of the database installation on your Data server.
http://www.microsoft.com/sql/prodinfo/previousversions/rs/howtolicensers.mspx
The server components of SQL Server 2000 Reporting Services include the Report Server and the Report Server Database. The Report Server processes and renders reports, and handles scheduled events and report delivery. The Report Server Database stores report definitions, report metadata, subscription information, and so on. Each Report Server requires either a local or remote connection to a Report Server Database. To use any of these components, each computer on which the Report Server and the Report Server Database are installed must have a valid SQL Server 2000 license.
You could install SQL Server Express on the application server.
It's free, and there's an edition which comes with Reporting Services.
In comparison with the "real" editions, SQL Server Express Edition is limited concerning how much CPU and RAM it can use, but it will probably be fast enough to run your reports.
blatantly incorrect. You do not need a SQL Server license to use SQL Server Reporting Services, you can use SQL Server Express edition. I've use SQL Server Express Edition in addition to linked servers-- to query stuff on -ANY- database server. And it works great.
SSRS is a great platform, I Just hate it when people run around saying that you NEED a license to use it. I'll bet that guy works for Oracle corp!
You do have an alternative. You can embed reports directly into your code projects in .Net. In this case the report runs through the Microsoft.Reporting.WinForms and Microsoft.Reporting.WebForms namespaces, ReportViewer object. Each report will have a ".rdlc" extension instead of ".rdl", though the two files types are actually equivalent. There is an ASP.Net version of the ReportViewer that allows you to integrate these reports into your website. You just need to drag the ReportViewer control from the toolbox into your website to configure it. For more information, see the MSDN overview of ReportViewer Controls.
If you dont want to use a whole license you can always use reportviewer. Just so I dont put too much answer out here, the big site for this is gotreportviewer.com.
The reportviewer control does the work of the reporting services server when it comes to the generation of reports. RDL files are like xml files and dont do much until they are interpreted. If you embed the reportviewer in your application on the web the work will be done on the user side. It is simialar to microsofts xps format, it has to be interpreted.
If you don't want to create an application for your reports the new version of sql2008 with advanced controls allows you to install a free version of reporting services. It doesnt have all of the goodies but it works for simple deployments.