Visual Studio Team Editon for DB Pro - Mairead's version

Here is a View that would not import correctly:

CREATE VIEW dbo.vLast10DaysCounterStats

AS

SELECT ProfileID, SUM(Total) AS Hits, CounterID

FROM dbo.CounterStats WITH (nolock)

WHERE (GMTDate >= DATEADD([day], - 10, Common.dbo.fnDateOnly(GETUTCDATE())))

GROUP BY ProfileID, CounterID

--

Team DB didn't recognize that Common.dbo.fnDateOnly is a User-Defined Function and throws error TSD4001 (SQL error = 4121)

Here is a View that would not import correctly:

CREATE VIEW dbo.vLayout

AS

SELECT StoreID, ProfileID, LayoutID, SectionID, LayoutName, 'Custom' AS Type, 1 AS TypeID

FROM dbo.CustomLayout WITH (NOLOCK)

UNION ALL

SELECT NULL as StoreID, NULL as ProfileID, LayoutID, SectionID, LayoutName, 'System' AS Type, 0 AS TypeID

FROM StoreStatic.dbo.StoreLayout WITH (NOLOCK)

UNION ALL

SELECT StoreID, ProfileID, -2 LayoutID, 4 SectionID, 'Default Item Detail Page Layout' LayoutName, 'Custom' AS Type, 1 AS TypeID

FROM dbo.Store WITH (NOLOCK)

--

Team DB reported:

TSD4001:  Invalid Object Name 'StoreStatic.dbo.StoreLayout'. (SQL Error = 208)

In production, we have many databases that reference objects from each other.  For the time being, let’s omit the discussion as to why this was done, or whether it was a good idea or not.

Assume we have 2 databases A and B.  Objects in A reference objects in B, and objects in B reference objects in A.  So I create a solution with 2 database projects, A and B.  Initially there are quite a few 3025 warnings about cross-database references that can’t be verified.  So, in project A, I set reference to project B.  The number of warnings is now cut in half.  This is good.  In project B, I try to set reference to project A, but it fails with the message:  “Adding this project as a reference would cause a circular dependency”.

Is this a know issue, and is it fixable?  Unfortunately this is a showstopper for us.

The install went flawlessly. I was able to update the projects and take out all the junk I had added for creating additional files, etc. It's great. The only nit I can pick is that I can't seem to find how to edit the logical name of the initial two files. Instead I added a rename to the post deployment structure script.

Mairead,

Adding a database reference solved both of the above issues.  My point was more along the lines of these should have been warnings like all of the other cross-database references, rather than an error.

Thanks for the response.

What you're suggesting doesn't work. That's the problem. Any files I create I can edit, but not the two initial ones?

We have an issue where we create 2 database projects, the first has a table which will be referenced in the second project.

The second project has a synonym for the table in the first project, create a view which uses the synonym in this project.

Build the database projects

Error: TSD4001: Invalid object name 'ACM.dbo.ROLES'. (SQL error = 208)

It cannot find the reference in this case for some reason??

We have an operational data warehouse.  It is a separate database and is managed by our Data Warehouse team.

All of the views in my database that reference the opwhse database are coming up with TDS4001 error.  Why is this an error and not a warning, like the other cross-database reference issues?

I'm not sure how to resolve this?  Or why I even should?  

Please advise.

We are in the early development stages of a migration effort from VB6/ASP to .NET.  We are not migrating any of the existing SQL 2000 databases in this process.  The databases used by this application are quite large, and have several dependencies on eachother.  The new SR helped us get over the first hurdle with the new Database Reference feature - love that.  Performance, though, is still not at an acceptable level for us to continue using this tool.  We are developing in a VPC, and our solution (containing a single DB project with references to dbmeta files for the other two DBs) takes about 5 minutes to load.  Build and deploy takes several minutes as well, depending on the volume of change.  Our VPCs are allocated 1GB out of the 2GB of RAM in our workstations, and notice very little problem with other VSTS tools in our development environment.

@Louise - I'm experiencing exactly the same problem with cross-database references in a view causing a TDS4001 error.  It's driving me crazy!