I have installed sharepoint 2010 with backend sql server 2008 R2 database name(wss_content). Now in my sharepoint site I have createed a sharepoint list( eg,customer). Now I want to access that list in the database(wss_content).
How can I access it?, and where can I see that list in wss_content.
Because I'm not able to see the list in the sql database.
There is no direct equivalent of the SharePoint list in the SQL Database - even though it's there. BUT you should never ever go into the SharePoint database and query for information - you'll likley get things wrong or mess things up.
Tell us what you need instead and we'll sort you out with the correct way to do it.
Related
How can I implement Anonymous Access for Reporting Service with SQL 2012?
Why on earth would you want to allow anonymous access to your report server in (I assume) a production environment.
If by 'anonymous access' you simply mean that want all users in your domain to be able to access the reports you publish to the report server (I'd think about this also - obviously I don't know where you work or what reports you are producing, but do you really want very junior staff seeing profit/loss accounts for example?) I suggest you start by reading the documentation here.
For my company there is a report that ends up in an access database format (.accdb) when it gets to my department. We want to deploy an SSRS with this information. While I was able to do it in Visual Studio the database manager questioned whether this can actually be deployed and work in the server environment. Can this this be achieved?
Are you talking about an Access report, or data inside of Access?
SQL server reports are not built in Access and have absolute nothing to do with Access. The only issue would be then since the report cannot be built in Access, then why attempt to have SQL server open an accDB file for the data source? You would be much better off to simply have Access transfer the table data to SQL server and then continue to use the reports built in SQL server.
So a report in Access has ZERO relationship to SQL server reports. As such, the reports in Access are of no use and if your plan is to use SSRS, then the reports have to be built in SSRS.
It is possible to place an Access accDB data file on the server and have SQL server connect such data, but it generally does not allow or work well with multiple users.
Keep in mind, the reverse is certainly possible and often recommended. You place and keep all data on SQL server tables. You then link the Access application to SQL server. In this setup then the data ALWAYS resides on SQL server, but the reports are in Access. And the general forms etc. built in Access will save + send their data to SQL server (and this works without having to write code).
The above thus suggests that the Access application with the reports has to be distributed to users that need such reports. And such users will thus all share only ONE copy of the data since such data resides on SQL server. And this setup would also allow one to create reports in SSRS without having to upload any kind of data, since the live operating data from the Access application always resides on SQL server.
So in summary:
Access reports are Access reports, just like FoxPro reports are FoxPro reports, and FileMaker reports are FileMaker reports. As such, these reports cannot be used, viewed, or utilized by SQL server in anyway.
However, the reverse is not only possible, but is a common solution. Thus the Access (front end) is linked to SQL server and the data tables for forms, code, reports etc. for the Access application now resides on SQL server.
If you place the actual accDB data file from Access ON the SQL server, then SQL server can read the data, but any code, forms, reports etc. from Access cannot be used by SQL server. So a report in Access is of ZERO use to SSRS.
So if SSRS is a goal, then anything built in Access from a user interface point of view cannot be used. SSRS thus can only consume the data in tables.
Since SSRS can ONLY consume data from Access (and nothing else), then a far better solution in place of moving up a accDB file to the server is to simply push up the data from Access tables to a SQL server tables. And if such a data transfer is to occur often, then likely better is to ALWAYS keep the tables and data in SQL server, and have the Access front end part “link” to the data on SQL server. Access reports, forms and even VBA code will in most cases run as before, but the live data always resides in SQL server. You thus eliminate all the dance and song of attempting to transfer data between two systems. The SQL server data is thus always “live” and update to date, and only ONE copy of the table data EVER exists.
Most Access applications and reports and forms can work with very few (if any) modifications when you place the data tables on SQL server, and have the front end Access part “link” to SQL server.
Since a given specialized report in SSRS is going to require a pre-determined and non changing table structure, then the most prudent solution would be to have Access link to and use the data from SQL server tables (not the other way around).
So Access reports can ONLY be used by those with Access (or the free runtime) installed on each client desktop computer. Such Access reports have to be 100% re-built if your goal is to have such reports be used with SSRS.
I am just starting out in ASP.NET with previous experience in C++ and was wondering if you can help me out/point me in the right direction here.
I know how to link an Access database to visual studio's web forms however when showing the data I have found the tables to be very ugly so wanted to populate classes with the data.
In my "product details" database are; product name, price, description, rating, cost etc.
Using this information from the database I understand that my code should attempt to connect to the database server then attempt to access the specified database schema.
By giving the database any table name I hoped to return an array of all rows with all data inside it, possibly within a function called selectingData? As it loops through each row, it stores the data as an associative array which is then saved as a new array element.
I could then apply some styling...
<div style="float:left; width:50%;"> ...logic of code... </div>
<div style="clear:both;"></div>
You should use Sql Server Express 2008 or 2012, might as well use 2012. Download and install, make sure to include Sql Server Management Studio with your installation package install. You can choose server only but you want the Sql Server Management Studio tool included in your install as well.
Sql Server Management Studio will easily import your Access database and make a Sql Database of it. Right click your localhost server after you install in Sql Server Management Studio and click Import and follow wizard options, there is a source type setting for Microsoft Access database.
From here you want to use Entity Framework 5 or 6 via Visual Studio 2012 or 2013. Visual Studio 2012 or 2013 Web Express are always free and the best IDE ever. You can generate a model of your imported access database. Just create a new ASP.NET Website (go with MVC) and then right click the project and select Add -> Add New Menu Item -> EF5.x or EF 6.x DbContext Generator. This will give you the functionality you need via Linq to query tables, get result sets, manipulate those result sets and bind them to your display HTML.
You might as well do things the right way since you are getting into ASP.NET. This path is a treat and easy to learn but you will have a day or two of a learning curve ahead of you.
I am trying to link a sharepoint list to another using sql server database. The ideal would be for this is to a live link so that when data in the sharepoint list is updated, the data in the sql server database is also updated. The reason that I need to do this is that I have an ASP page which will query the SQL database and display the results on a web page.
Any guidance would be much appreciated
Thanks in advance
SidJ
PS : I have done this in access before using the External Data tab ->
More -> Sharepoint List and then following the steps in the wizard, so
I know it is possible. Just not sure how to recreate this using SQL
Server as the destination for the data.
You can go BCS (Business Connectivity Services) or build something custom using a connector like http://www.bendsoft.com/net-sharepoint-connector/
Here is a small guide on BCS http://zimmergren.net/technical/sp-2010-programmatically-work-with-external-lists-bcs-in-sharepoint-2010
I would like to know the easiest and fastest way to retrieve data from SQL Server 2008 R2 via Sharepoint 2010.
I am new to sharepoint but have been able to create an external content type using Sharepoint designer which connects to the database in SQL Server but I have not been able to use the business web chart to relay the data gotten from the database.
I want to relay information from a customer service database into sharepoint and want it to be consistent.
Is this the best way to go about it or is there a better way?
Many thanks for your usual cooperation and response.
Cheers,
Tunde
Your best bet is SQL Server Reporting Services, which will need to be installed in Sharepoint integrated mode. It does not have to be 2008 R2, it can be 2008, and the good news is that if you run reporting services on the same server as your SQL databases, you're already licenced for it.
Take a look at http://www.bidn.com/ for more answers, or ask questions using the #SQLHelp tag on twitter for SSRS, or #SPHelp for sharepoint