Comments
Sort by recent activity
sorry to reopen an old thread but I am having this same problem with prompt 3.9 - it hands for a long time on reading object text.
this is using sql express 2005. running select * from sys.sql_modules only returns about 35 records and it returns them virtually instantly. / comments
sorry to reopen an old thread but I am having this same problem with prompt 3.9 - it hands for a long time on reading object text.
this is using sql express 2005. running select * from sys.sql_modu...
ok thanks. at least i know i wasnt doing anything wrong [image] / comments
ok thanks. at least i know i wasnt doing anything wrong
Thanks - is there a link to view all pending feature requests? / comments
Thanks - is there a link to view all pending feature requests?
I guess this isn't a very high priority request considering that feature request is from may of 2011 ;)p I voted for it anyhow though. / comments
I guess this isn't a very high priority request considering that feature request is from may of 2011 ;)p I voted for it anyhow though.
I did run into some issues - there was one stored proc which is was listing as conflicting and would not allow me to tell it to just over-write the sproc in source control.
I had to delete the sproc from my db, get it from source control, apply changes and then commit it.
The folder structure did not change, it just moved down one level.
i.e. /project/sql became /trunk/project/sql
I think it might be nice to have an option to just be able to update the source control url, rather then having to delink/relink the db.
thanks / comments
I did run into some issues - there was one stored proc which is was listing as conflicting and would not allow me to tell it to just over-write the sproc in source control.
I had to delete the spro...
here's the full sql USE [MachineSales]
GO
/****** Object: StoredProcedure [dbo].[spViewProductStatisticByUserID] Script Date: 8/3/2012 1:48:00 PM ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
ALTER PROCEDURE [dbo].[spViewProductStatisticByUserID]
@ID INT,
@StartRow INT,
@PageSize INT
AS
BEGIN
SET NOCOUNT ON
SELECT p.[ID], p.[Title], p.[ShortDescription], p.[Price], img.[ImageThumbID] AS [ImageID], ps.[SearchResults], ps.[PageViews], ps.[PhoneClicks], ps.[EmailClicks], ps.[WebsiteClicks],
p.[Modified], p.[ModifiedBy], p.[Created], p.[CreatedBy]
FROM [Product] AS p
INNER JOIN [ProductStatistic] AS ps ON ps.[ProductID] = p.[ID]
LEFT JOIN [ProductImage] AS img ON img.[ProductID] = p.[ID] AND img.[SortOrder] = (SELECT MIN([SortOrder]) FROM [ProductImage] WHERE [ProductID] = p.[ID])
WHERE p.[Deleted] = 0
AND p.[UserID] = @ID
ORDER BY p.[Created],p.[ID] DESC
OFFSET @StartRow ROWS
FETCH NEXT @PageSize ROWS ONLY
END
/ comments
here's the full sqlUSE [MachineSales]
GO
/****** Object: StoredProcedure [dbo].[spViewProductStatisticByUserID] Script Date: 8/3/2012 1:48:00 PM ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFI...
David Atkinson wrote:
merk - that's useful information. You're using filtering to ignore known stored procedure differences as a workaround for linked server name references. This is an issue we anticipated, but so far we've not had anyone bring it up just yet. I'd be very interested in hearing from any other users who are experiencing this. Clearly, if this is a pervasive issue, we should be looking at addressing the root cause and devising a mechanism where these different server name references aren't regarded as actual differences.
well ideally, it would be nice if i could specific a string that would get auto-replaced when moving from one server to another.
ie on dev it's linkdevserv. DevDb.dbo.devtable
and when i'm pushing changes to the production db, it should automatically convert linkdevsrv to linkprdserv and devdb to proddb, and should ignore differences in that text when doing a compare.
I didn't think that would be something that would be included in sql source control, which is why i asked about ignoring files, which is obviously an imperfect workaround. / comments
David Atkinson wrote:
merk - that's useful information. You're using filtering to ignore known stored procedure differences as a workaround for linked server name references. This is an issue w...
For me, in this instance, i have linked servers and the server names/db names differ between dev and production. So my stored procs will always be slightly different between dev and production. I couldn't find a way to use some sort of aliasing system so that i could keep the stored procs in sync. So right now i always have some stored procs showing up as needing to be committed, or updated, since they have different linked server names in them.
i also occasionally comment out sections of code in my dev or prod stored procs since some of it's for debugging purposes. / comments
For me, in this instance, i have linked servers and the server names/db names differ between dev and production. So my stored procs will always be slightly different between dev and production. I c...
I am indeed talking about sql source control. Is this something that's going to be added in? / comments
I am indeed talking about sql source control. Is this something that's going to be added in?