May 2008 - Posts
1. Visual Studio 2008 SP1 is already in a beta and can be downloaded from
here2. if you just want to download .NET 3.5 SP1 beta, it can be downloaded from
here3. Lot of enhancements and bugs fixes have been done. Overview of the same can be seen at
here4. There is a dedicated Microsoft forum for VS 2008 SP1 beta and can be visited at
hereIf you are one of the Vista users using VS 2008, and want to download the VS 2008 SP1. There are some issues related to installing .NET 3.5 SP1 on Vista RTM so better recommended approach is to install the SP 1 of Vista before installing VS 2008 SP1.
Last weekend, got some good time to write an article on sharepoint workflow wizard in VS 2008. The article gives a brief detail on
1. Sharepoint workflows in VS 2008
2. Sharepoint workflow wizard in VS 2008 and its Pros/Cons
You can get it available from the below URL of code project site
http://www.codeproject.com/KB/WF/sharepointworkflow.aspx
Visual Studio 2008 provides lot of workflow templates. if you see the screen , two of those belong to Sharepoint.
1. SharePoint 2007 Sequential Workflow
2. SharePoint 2007 State Machine Workflow
Sequential workflow represents a workflow as a sequence of steps that must be executed in order until the last activity is completed. A state machine workflow represents a set of states, transitions, and actions. One state is denoted as the start state, and then, based on an event, a transition can be made to another state. Below is a typical example of a Sequential workflow.
.png)
when you select any of these workflow template, it executes the workflow wizard that allows to do debugging on the workflows on sharepoint that requires special permissions. for e.g this wizard takes care of deploying workflow customization on Global Assembly Cache (GAC). Wizard also takes care of associating the associate the workflow template with a document library or list. It how an instance of your workflow can be started. Without VSTO you need to handle this outside of Visual Studio in separate steps. Not only this, this workflow can be very well debugged inside visual studio. Really i would say that with lots of inclusion of sharepoint related work in Visual Studio, Microsoft is really making the life ease of the developers.
Yesterday after downloading a software, the word that came from my mouth is "WOW" .. well , its
NOT VISTA, my dear friends... it is
World Wide Telescope from Microsoft Research. Microsoft Research team has came up with the product called World Wide Telescope, built on .NET framework 2.0. Presently it is in beta . You can install it in your machines and make your machine as a telescope. You can navigate to any place, any part, universe, glaciers etc .. Its really really awesome . this is far more superior to Google earth, Virtual earth etc..This product is been based on Web 2.0 Visualization technology ( one of the promising and upcoming technologies ) . WorldWide Telescope is created with the Microsoft® high performance Visual Experience Engine™ and allows seamless panning and zooming around the night sky, planets, and image environments. If you have a 3d Graphics card, .NET 2.0 and DirectX, download and get a glimpse of the beautiful world around.
http://www.worldwidetelescope.org/ .
The
following table lists the recommended guidelines for site objects.
Site object
|
Guidelines for acceptable performance
|
Notes
|
Site
collection
|
50,000
per Web application
|
Total
farm throughput degrades as the number of site collections increases.
|
Web
site
|
250,000
per site collection
|
You
can create a very large total number of Web sites by nesting the subsites.
For example, 100 sites, each with 1000 subsites, is 100,000 Web sites. The
maximum recommended number of sites and subsites is 125 sites with 2,000
subsites each, for a total of 250,000 sites.
|
Subsite
|
2,000
per Web site
|
The
interface for enumerating subsites of a given Web site does not perform well
as the number of subsites surpasses 2,000.
|
Document
|
5
million per library
|
You
can create very large document libraries by nesting folders, using standard
views and site hierarchy. This value may vary depending on how documents and
folders are organized, and by the type and size of documents stored.
|
Item
|
2,000
per view
|
Testing
indicates a reduction in performance beyond two thousand items. Using
indexing on a flat folder view can improve performance.
|
Document
file size
|
50MB
(2GB max*)
|
File
save performance is proportional to the size of the file. The default
maximum is 50 MB. This maximum is enforced by the system, but you can change
it to any value up to 2 GB.
|
List
|
2,000
per Web site
|
Testing
indicates a reduction in list view performance beyond two thousand entries.
|
Field
type
|
256
per list
|
This
is not a hard limit, but you might experience list view performance
degradation as the number of field types in a list increases.
|
Column
|
2,000
per document library4,096 per list
|
This
is not a hard limit, but you might experience library and list view
performance degradation as the number of columns in a document library or
list increases.
|
Web
Part
|
50
per page
|
This
figure is an estimate based on simple Web Parts. The complexity of the Web
Parts dictates how many Web Parts can be used on a page before performance
is affected.
|
The
following table lists the recommended guidelines for people objects.
People object
|
Guidelines for acceptable performance
|
Notes
|
Users
in groups
|
2
million per Web site
|
You
can add millions of people to your Web site by using Microsoft Windows
security groups to manage security instead of using individual users.
|
User
profile
|
5
million per farm
|
This
number represents the number of profiles which can be imported from a
directory service, such as Active Directory, into the people profile store.
|
Security
principal
|
2,000
per Web site
|
The
size of the access control list is limited to a few thousand security
principals (users and groups in the Web site).
|
The
following table lists the recommended guidelines for search objects.
Search object
|
Guidelines for acceptable performance
|
Notes
|
Search
indexes
|
One
per SSPMaximum of 20 per farm
|
Office
SharePoint Server 2007 supports one content index per SSP. Given that we
recommend a maximum of 20 SSPs per farm, a maximum of 20 content indexes is
supported. Note that an SSP can be associated with only one index server and
one content index. However, an index server can be associated with multiple
SSPs and have a content index for each SSP.
|
Indexed
documents
|
50,000,000
per content index
|
Office
SharePoint Server 2007 supports 50 million documents per index server. This
could be divided up into multiple content indexes based on the number of
SSPs associated with an index server.
|
Content
sources
|
500
per SSP*
|
This
is a hard limit enforced by the system.
|
Start
Addresses
|
500
per content source*
|
This
is a hard limit enforced by the system.
|
Alerts
|
1,000,000
per SSP
|
This
is the tested limit.
|
Scopes
|
200
per site
|
This
is a recommended limit per site. We recommend a maximum of 100 scope rules
per scope.
|
Display
groups
|
25
per site
|
These
are used for a grouped display of scopes through the user interface.
|
Crawl
rules
|
10,000
per SSP
|
We
recommend a maximum 10,000 crawl rules irrespective of type.
|
Keywords
|
15,000
per site
|
We
recommend a maximum of 10 Best Bets and five synonyms per keyword.
|
Crawled
properties
|
500,000
per SSP
|
These
are properties that are discovered during a crawl.
|
Managed
properties
|
100,000
per SSP
|
These
are properties used by the search system in queries. Crawled properties are
mapped to managed properties. We recommend a maximum of 100 mappings per
managed property.
|
Authoritative
pages
|
200
per relevance level
|
This
is the maximum number of sites in each of the four relevance levels.
|
Results
removal
|
100
|
This
is the maximum recommended number of URLs that should be removed from the
system in one operation.
|
Crawl
logs
|
50,000,000
|
Number
of individual log entries in the crawl log.
|
The
following table lists the recommended guidelines for logical architecture
objects.
Logical architecture
object
|
Guidelines for acceptable performance
|
Notes
|
Shared
Services Provider (SSP)
|
3
per farm (20 per farm maximum)
|
|
Zone
|
5*
per farm
|
The
number of zones defined for a farm is hard coded to 5.
|
Web
application
|
99
per SSP
|
This
limit includes the number of Web applications on child farms consuming
resources on this SSP.
|
Internet
Information Services (IIS) application pool
|
8
per Web server
|
Maximum
number is determined by hardware capabilities.
|
Site
collection
|
50,000
per Web application
|
|
Content
database
|
100
per Web application
|
|
Site
collection
|
50,000
per database
|
|
The
following table lists the recommended guidelines for physical objects.
Physical object
|
Guidelines for acceptable performance
|
Notes
|
Index
servers
|
1
per SSP*
|
|
Application
servers running Excel Calculation Services
|
No
limit
|
|
Query
servers
|
No
limit
|
Because
100 content databases are supported for each query server, the number of
query servers required per farm is based on the number of content databases
in the farm. For example, if there are 500 content databases in your farm,
you will need at least 5 query servers.
|
Web
server/database server ratio
|
8
Web servers per database server
|
The
scale out factor is dependent upon the mix of operations.
|
Web
server/domain controller ratio
|
3
Web servers per domain controller
|
Depending
on how much authentication traffic is generated, your environment may
support a greater number of Web servers per domain controller.
|
Reference has been taken from http://technet.microsoft.com/en-us/library/cc262787.aspx