StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2269703
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-02-15T23:31:27.073
FavoriteCount
0
LastActivityDate
2010-02-15T23:38:46.640
LastEditDate
2010-02-15T23:38:46.640
LastEditorUserId
171812
OwnerUserId
171812
ParentId
2265019
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
In that case the answer most likely lies with the use of Sql Server SYNONYMS which are like aliases. This article <a href="http://www.mssqltips.com/tip.asp?tip=1076" rel="nofollow noreferrer">How and why should I use SQL Server 2005 synonyms?</a> has an introduction to them. You basically want to: <pre><code>CREATE SYNONYM [dbo].[aspnet_CheckSchemaVersion] FOR [yourschema].[aspnet_CheckSchemaVersion] </code></pre> For each affected object. This could be time consuming so this script will likely be of some benefit: <pre><code>SELECT 'CREATE SYNONYM [dbo].[' + p.Name + '] FOR [' + s.Name + '].[' + p.Name + ']' FROM sys.Procedures p INNER JOIN sys.Schemas s on p.schema_id = s.schema_id </code></pre> You need to copy paste the output of the above script into a new script window and execute that. So the idea is that you're using a script to generate other script commands. If you then execute the output of the above script, it will then create synonyms for all procedures in the db. So note: <ol> <li>It assumes you have a db with only Application Services procs in it. If you have your own custom procs in there then you will have to add a WHERE conditional to filter for only Application Services objects which start with 'aspnet_' i.e. WHERE p.name LIKE 'aspnet_%'.</li> <li>This procedure assumes you've already done a find and replace to setup your new schema. i.e. generated a database script from the original db, done a find and replace on the dbo schema references, then delete/drop original dbo objects, and then run the amended script to get the [schema].[object] setup you want, and then finally use the scripts above.</li> <li>The performance cost of using SYNONYMs will be application dependant. </li> </ol> Sounds like a lot of trouble but the whole procedure will probably take you 3-4 mins.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POConfigure ASP.NET Application services to use a schema other than 'dbo'
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USintermension
UserOwnerUserId
1. USintermension
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POConfigure ASP.NET Application services to use a schema other than 'dbo'
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.