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.
Related
I've been tasked to create a search function for a websites' knowledgebase (which is stored in a github repo). I'm only really familiar with building databases with Django, so I'm having trouble understanding how I'm supposed to upload a bunch of html files to the database and query them with postgres. Any pointers on how the database can be structured. I've heard that html files can be stored in a text field, but how are the columns structured, does each page get its' own row, etc? and how can I do this with a fairly large knowledge base without having to manually upload each file?
The db hosting platform I am using has a migration utility that says
Uploading will accept data in any of three forms, plain text (SQL), tar archives (uncompressed), or PostgreSQL's own compressed 'custom' format.
That's assuming the database is already structured.
I've heard that html files can be stored in a text field, but how are the columns structured, does each page get its' own row, etc?
Storing html in a column is perfectly acceptable. If you're storing the html in a column, then each new page requires a new row.
and how can I do this with a fairly large knowledge base without having to manually upload each file?
You just said the hosting provider permits "PostgreSQL's own compressed 'custom' format". So install PostgreSQL locally. Get it all up and working. Insert every page locally. Then you can upload to the hosting provider using pg_dump --format=c which is not just a single action, but compressed.
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/
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...
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
I am building a personal site, for a blog I wish to use WordPress and for a wiki i will use
wikia. Is it possible that i use the same database for storing articles from both frontends (WordPress and wiki). If yes can i some how populate articles from my wiki to the blog, under a specific category.
EDIT-- By two different sites I mean two different frontends, hosted at different subdomains.
At installation time, both WordPress and Wikka allow you to prefix their tables with different names to prevent naming collisions. So yes it is possible to allow both applications to share the same database.
We have plenty of customers on our shared hosting environment who do this without any issues.
In answer to your second question, you may be in for a bit of custom code to do that.
Why not, its possible, just take care from any tables names conflict between both tables, you may need to edit some tables names.
And about populating one from another, i think you will need to edit its code some how to let it understand the new tables.
A host will put multiple clients on the same database server, so yes.
If you control the database and the apps, then you could code them to "share info"
They can quite happily use the same database. Depending on the RDBMS you are using, you may want to create an additional Database or user instance for each site.
With SQL Server you can create an additional database, or you can add a schema for each site. for Oracle you can create a user specific to each site.
To return data from one place to another, simply build a view which is accessible to each schema. You will need to set privileges on the source database to do this, but that's pretty straightforward.
The short answer is YES.
However, you will need to watch out for database object naming conflicts.
Also, when you say 'two different sites' do you mean 2 different sites? Or just different 'frontends' within the same site? If it just different front apps running in the same website, then you will also have to make sure you won't have any configuration conflicts.
I'm not really sure what your aim is. Is your intention simply to share data between Wordpress and Wikia?
You should not store two unrelated schemas in one database. It's just asking for collisions. Both Wikia and Wordpress maintain their own schemas: they may name different functional database objects the same.
If you want to share data between the two databases, you can set up triggers and views to move data from one to the other without them being in the same database.