Is it possible to view and update metadata from SQL Server in SharePoint?
I’m asking because I would like to create a SharePoint site where I have a “library” that can search for all sorts of databases based on keywords, etc… and I would like the metadata of a desired search result (.dbo metadata) to appear and allow it to be editable IN SharePoint (without having to go to SQL Server and do it there- AND at the same time, the changes would automatically register in SQL server as well).
Is this possible?
Have you considered storing your metadata 'tags' in a sharepoint list (or maybe differet categories of metadata in several sharepoint lists) and then using a lookup field (linked to your sharepoint 'tags' lists) which allows multiple items to be selected as a metadata in a field (or several fields) against the documents in the document library? That way you keep your metadata managed nice and easily in sharepoint and can filter the documents author any custom development?
Hope this helps or at least gives you another option for the way you look at solving your problem...
Related
I was wondering if this is something thats possible: currently I use this clickonce application to generate .ini files of access tables, I started learning vb.net not too long ago and I was wondering if I can replicate this utility via a vb.net form/app? Since currently not all the users in my company can use this utility for whatever reason by upper management and I looked around this site and other places, I found resources on how to create schema .ini files but what if the schemas are already in an sql table?
So for example each type of client has a code and schema type in our sql tables with "pick up locations", we use this in the click once app where I can select the access db, the table, and the location to drop off the created .ini file.
Currently in the sql, I have all the schemas in the schema table that has 3 different schemas and we tie the clients to one of these with each schema having different field order, length, type etc.
I want to be able to create a form and the user would be able to input the location of the access db and the table to be converted, then the client name (from a drop down) and based on the client the vb.net app would generate the correct schema ini file in the location for that client. Is this possible? I just dont want to keep looking into something if its not something achievable. Any information is greatly appreciated thank you
We'd like to set up a site subscription but the 200gb limit content db is holding us back. Can we use multiple content databases?
A content database is associated with a Site Collection. You have full control on which Content DB the Site Collection will get created. I am not a site subscription expert, but I went through a couple of quick articles http://blogs.technet.com/b/speschka/archive/2009/12/30/multi-tenancy-in-sharepoint-2010-part-2.aspx, and it appears that you create site collections for that. Hence, my calculated guess is that it should be possible to have multiple content database.
Keep in mind that to create a Site Collection into a specific content DB, the other content DBs should be made offline from Central Admin. http://littletalk.wordpress.com/2008/10/10/creating-a-site-collection-in-a-new-content-database/
I want to create multiple document libraries under the same site collection in sharepoint. However i would like to be able to specify different content databases for these document libraries - is that possible?
Example.
Site - TestSite has multiple content databases Content_1 and Content_2.
TestSite has two document libraries Documents_A and Documents_B.
Is there a way i can have Documents_A stored in Content_1 and Documents_B in Content_2?
Thanks
As far as I know, a web application can have multiple content databases, but a site collection can only be stored on a single database.
You can choose the database in which a site will be stored by using this trick.
We're just starting Sharepoint development, and one of my first tasks is to build a data collection tool. It will be used across multiple sites, so there will be an admin area, and each site will pull in it's related questions, and record the data. I've gone through a bunch of tutorials on development, and have a fairly good idea of how to start. I just want to make sure I understand one thing. Do lists basically take the place of your database? If this was a regular app, I would create a question table, a link table that tells which questions are connected to which site, a table that stores the answer, linking to the site and question table.
Is this the basic pattern you follow, or should I be doing things differently for Sharepoint applications?
If the thought is to use an external databse, can anyone point me to some info on this?
In our Sharepoint project we stared with Lists. It was good to some point - till DB had only few relations between data. After adding tables and relations performance falls a lot and we had to switch to use standard DB in MS SQL Server. So I recomend to use DB.
Disadventages: you cannot use sharepoint controls to edit/view data and cannot restrict access to data from sharepoint level
Adventages: much faster access to data
We've got some relational data in SQL Server and would like to build a UI in Sharepoint 2010 to create and modify records. For simple tabular data it's straightforward, but what about master-detail structures where a single logical object is com posited from a number of tables?
A large topic, but is there a basic course of action that is best?
If you create external content types, you can add associations between them that correspond to the relations between the tables in your database. For each external content type, create an external list that you can use for adding/updating/deleting your data.
For displaying master/detail records, you could add multiple webparts on a page and create connections between them. By creating the connection, the list displaying detail records will be filtered after selecting a master record.
If your database has m-n relations, you'll want to create your external content types in Visual Studio because SharePoint Designer 2010 only supports 1-n relations.
I don't know if it's the best way, but BCS is a big improvement over BDC and I think it can cover most if not all of your requirements. (depending on the complexity of your data)