Home of the Data Dude

Just a quick note for those of you who are lucky enough to work with VSDBPRO. Service release 1 is available,

Confused about DataDude - I use VS professional.  Is Datadude just another addin allowing me to create db projects, or is it a completely separate dev product? Does it require team foundation server? If I wait for VS 2008 is it included in the professional version?

Thanks for any clarifications.

The Accentient Blog on Using Project to enter "Resources". GertD on Service Release 1 is here! Grant...

Hi,

I'm pleased to see SR1 available because I needed it for variables support. But I'm surprised to see that variables can only be used in a restricted context.

There is my need in post-deployment scripts :

IF $(DEBUG) = 1

 Begin

 --test data for development environment

 INSERT INTO dbo.myTable VALUES('some data')

 End

But $(DEBUG) used as described upper generates an error at parsing.

The workaround I use is :

Declare @debug as int

select @debug = cast('$(DEBUG)' as int)

if  @debug = 1

print 'DEBUG MODE!!!'

Anymore smart solution ?

The team that builds Visual Studio Team Edition for Database Professionals (or “DBPro” for short!) has

Gert Drapers and I recently sat down to film a Channel 9 interview showcasing the new Service Release

If you want to document your database you've got to see Gert Drapers on Channel9. Data Dude is answering

My blog has moved to sqlblogcasts.com/blogs/simons

The full version of this post can be found here.,...

Just a quick note for those of you who are lucky enough to work with VSDBPRO. Service release 1 is available

Is there support for UPDATE FROM syntax with SP1?  It appears the parser does not handle an alias well.  This leads to hundreds of warnings for me.  Snippet from a sample:

update

[Security].[dbo].[AdUsers]

set

userid = s.userid,

domain = s.domain,

status = s.status,

...

from

[Security].[dbo].[AdUsersStage] s

where

[Security].[dbo].[AdUsers].guid = s.guid

and

[Security].[dbo].[AdUsers].lastupdate < s.lastupdate

The stage table is aliased as "s" since it has columns identical to those in AdUsers.

The warning thrown is:

Warning 1 TSD3006: The relationship from [Procedure] dbo.admsp_adsynch cannot be resolved between the following possible identifiers: [Column] Security.dbo.AdUsersStage.s, [Column] Security.dbo.AdUsersStage.userid, [Column] Security.dbo.AdUsers.s. C:\Documents and Settings\douglma\My Documents\Visual Studio 2005\Projects\Test\Security Database\Security Database\Schema Objects\Stored Procedures\dbo.admsp_adsynch.proc.sql 22 11 Security Database