Comments
Sort by recent activity
Source control seems to be having problems commiting bindings:
EXEC sp_bindefault N'[dbo].[GPS_CHAR]', N'[dbo].[USA_DYNTableDefWork].[rSysTablePhysicalName]'
GO
EXEC sp_bindefault N'[dbo].[GPS_CHAR]', N'[dbo].[USA_DYNTableDefWork].[rSysFieldName]'
GO
EXEC sp_bindefault N'[dbo].[GPS_CHAR]', N'[dbo].[USA_DYNTableDefWork].[rSysField1]'
GO
This is the issue on each of the 6 tables that will not commit. / comments
Source control seems to be having problems commiting bindings:
EXEC sp_bindefault N'[dbo].[GPS_CHAR]', N'[dbo].[USA_DYNTableDefWork].[rSysTablePhysicalName]'
GO
EXEC sp_bindefault N'[dbo].[GPS_CHAR...
Any ideas? / comments
Any ideas?
The query timeout was already set to unlimited.
I ran a trace on the server that was getting the timeout in source control and the following statement continues to run over and over even after the application return the timeout statement.
-- Copyright © 2009 – 2012 Red Gate Software Ltd.
SET XACT_ABORT ON ;
SET LOCK_TIMEOUT 100 ;
BEGIN TRAN ;
IF OBJECT_ID(N'tempdb..#RG_NewSysObjects', N'U') IS NOT NULL
DROP TABLE #RG_NewSysObjects ;
SELECT *
INTO #RG_NewSysObjects
FROM [DYNAMICS].sys.objects ;
SELECT ls.name AS prevName ,
curr.name AS name ,
ls.object_id AS prevId ,
curr.object_id AS id ,
ls.SchemaName AS prevSchemaName ,
sysSchemas.name AS schemaName ,
ls.type AS prevType ,
curr.type AS type
FROM #RG_LastSysObjects AS ls
FULL OUTER JOIN #RG_NewSysObjects AS curr ON ls.object_id = curr.object_id
LEFT JOIN [DYNAMICS].sys.schemas AS sysSchemas ON sysSchemas.schema_id = curr.schema_id
WHERE ( curr.type IS NULL
OR curr.type NOT IN ( 'C', 'D', 'F', 'IT', 'PK', 'S', 'TA', 'TR', 'TT', 'UQ' )
OR ( curr.type = 'D'
AND curr.parent_object_id = 0
)
)
AND ( ls.modify_date <> curr.modify_date
OR ls.object_id IS NULL
OR curr.object_id IS NULL
OR ls.name <> curr.name --TODO schema/type changes
)
ORDER BY curr.modify_date ;
IF OBJECT_ID(N'tempdb..#RG_LastSysObjects', N'U') IS NOT NULL
DROP TABLE #RG_LastSysObjects ;
SELECT sysObjects.object_id ,
sysSchemas.name as SchemaName ,
sysObjects.name ,
sysObjects.type ,
sysObjects.modify_date
INTO #RG_LastSysObjects
FROM #RG_NewSysObjects AS sysObjects
LEFT JOIN [DYNAMICS].sys.schemas AS sysSchemas ON sysSchemas.schema_id = sysObjects.schema_id
WHERE sysObjects.type NOT IN ( 'C', 'D', 'F', 'IT', 'PK', 'S', 'TA', 'TR', 'TT', 'UQ' )
OR ( sysObjects.type = 'D'
AND sysObjects.parent_object_id = 0
) ;
COMMIT ; / comments
The query timeout was already set to unlimited.
I ran a trace on the server that was getting the timeout in source control and the following statement continues to run over and over even after the ...
Any ideas? / comments
Any ideas?
This works great on large databases with many encrypted stored procedures. Without setting the "DecryptPost2kEncryptedObjects" to false, it would take 30+ minutes for Source Control to look for our changes. Thanks for sharing this! / comments
This works great on large databases with many encrypted stored procedures. Without setting the "DecryptPost2kEncryptedObjects" to false, it would take 30+ minutes for Source Control to look for our...
It seems to have worked correctly with the command line and the /alldbs flag set. However, it did have a problem with a database that I had set to OFFLINE since the last time the project file was opened in the UI. / comments
It seems to have worked correctly with the command line and the /alldbs flag set. However, it did have a problem with a database that I had set to OFFLINE since the last time the project file was o...
Thanks Guys! BTW, we love your products. Keep up the good work! / comments
Thanks Guys! BTW, we love your products. Keep up the good work!
James, thank you for your reply.
We are using our development environment for smaller unit testing. Once testing is done on that level, it is moved to PreProduction for larger system testing.
In our development environment, we use a shared database between multiple developers. What I'm worried about if we sourced from that point is security. I dont want developers checking in changes that haven't been approved or checked. I'm guessing that can be managed on the TFS level. / comments
James, thank you for your reply.
We are using our development environment for smaller unit testing. Once testing is done on that level, it is moved to PreProduction for larger system testing.
In ou...
the latter would be most useful / comments
the latter would be most useful