Comments
Sort by recent activity
I'm curious how that price came about considering SQL Bundle Standard is $490.
Sql Bundle Std is something I'd expect to cost $500. Sql Refactor/Prompt is not.
Would this include life-time updates? / comments
I'm curious how that price came about considering SQL Bundle Standard is $490.
Sql Bundle Std is something I'd expect to cost $500. Sql Refactor/Prompt is not.
Would this include life-time updates?
I'm glad to have had this beta. And although a second beta would be nice, I'm guessing the final version will be great. After all, the other red-gate products I use turned out great even w/o my input. :-)
Unless 3.0 is perfect with no bugs or missing features <chuckle><chuckle>, I hope the 3.x versions keep coming out on a regular basis. / comments
I'm glad to have had this beta. And although a second beta would be nice, I'm guessing the final version will be great. After all, the other red-gate products I use turned out great even w/o my inp...
I think several of your issues are being addressed in the final version.
I think I read that they are not going to have another beta version before release, which is too bad because i'm guessing the beta version we are running is nothing like the current version. / comments
I think several of your issues are being addressed in the final version.
I think I read that they are not going to have another beta version before release, which is too bad because i'm guessing th...
1. Open the original Sql.
2. Choose "Lay Out Sql"
3. Get lineIndex exception, click contine.
4. Comment out USE statement.
5. Choose "Lay Out Sql"
6. Get lineIndex exception, click contine.
7. Remove "--"
8. Choose "Lay Out Sql", No Error
9. Un-Comment USE statement
10. Choose "Lay Out Sql", No Error
11. Put "--" back.
12. Choose "Lay Out Sql", No Error
In the end I have the same Sql statements, except there is no error. The only text I add/remove is the comment lines before the USE statement and in the WHERE clause.
After running the first "Lay Out Sql" I get this: LINE 1: USE SiteSecurity_Secure
LINE 2:
LINE 3: SELECT dbo.OrganizationClasses.OrgClassCode, [+ rest of the file, Including entire WHERE clase]
After going through the above procedure I get this: LINE 1: USE SiteSecurity_Secure
LINE 2:
LINE 3: SELECT dbo.OrganizationClasses.OrgClassCode, [+ rest of file, up to the comment in the WHERE clause
LINE 4: -- AND ( b.CreateDate < @DATEB ) [+ remainder of file]
/ comments
1. Open the original Sql.
2. Choose "Lay Out Sql"
3. Get lineIndex exception, click contine.
4. Comment out USE statement.
5. Choose "Lay Out Sql"
6. Get lineIndex exception, click contine.
7. Remo...
This is the contents of the file I was dealing with. If I paste the following into a new query window in Sql Mgt I get the same error as soon as I do the paste.
If I un-comment the comment in the WHERE clause and then paste the query it works just fine. Definatly has something to do with the comment.
If I mess up the formatting, then choose "Lay Out Sql" the formatting is correct, and then I get the error again.
If I delete the "--" while in Sql Mgt then all is well. Add the comment back by typing "--" and the error pops up again.
I had previously posted about how the missing CR/LF causes errors with comments.
Get me your email and I can send you the original file if you want it. DECLARE @DATEA DateTime ;
SET @DATEA = '7/01/2006'
-- DECLARE @DATEB DateTime ;
-- SET @DATEB = '8/01/2006'
USE SiteSecurity_Secure
SELECT dbo.OrganizationClasses.OrgClassCode,
o.OrgName,
COUNT(s.SearchID) AS CountOfSearchID
FROM dbo.BatchLog b WITH ( nolock )
INNER JOIN dbo.SearchLog s WITH ( nolock ) ON b.BatchID = s.BatchID
INNER JOIN dbo.SearchItems si WITH ( nolock ) ON s.SearchID = si.SearchID
INNER JOIN dbo.Organizations o WITH ( nolock ) ON b.OrgID = o.OrgID
INNER JOIN dbo.Organization_To_OrganizationClass WITH ( nolock ) ON o.OrgID = dbo.Organization_To_OrganizationClass.OrgID
INNER JOIN dbo.OrganizationClasses WITH ( nolock ) ON dbo.Organization_To_OrganizationClass.OrgClassID = dbo.OrganizationClasses.OrgClassID
WHERE s.SearchLogStatus <> 'E'
AND b.BatchStatus <> 'E'
AND ( si.ItemTypeID = 2 )
-- AND ( b.CreateDate < @DATEB )
AND ( b.CreateDate >= @DATEA )
GROUP BY
dbo.OrganizationClasses.OrgClassCode,
o.OrgName
ORDER BY
dbo.OrganizationClasses.OrgClassCode,
o.OrgName
/ comments
This is the contents of the file I was dealing with. If I paste the following into a new query window in Sql Mgt I get the same error as soon as I do the paste.
If I un-comment the comment in the W...
There's going to be another Beta? When? / comments
There's going to be another Beta? When?
I have received this error several times also. I suspect it has something to do with when there is a commented line.
For a while I was getting it all the time -- seems to be better today (And I have not rebooted).
Perhaps it was a specific file I was working on. I'll try to pay better attention. / comments
I have received this error several times also. I suspect it has something to do with when there is a commented line.
For a while I was getting it all the time -- seems to be better today (And I hav...