Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
SQL Fixes
#1
Hello

Is it planned to fix the following SQL "issues" in the next version?

[We use ASG 11.0.5988.1 in combination with SQL Server 2016 SP1
We've used the Microsoft Data Migration Assistent to create an assessment.]

issues:

tables:
ItemProperties --> column Data is ntext => change to nvarchar(max)
Items --> column Description is ntext => change to nvarchar(max)
Logs --> column Details is ntext => change to nvarchar(max)

procedures:
"Old WHERE syntax"
Code:
ALTER PROCEDURE [dbo].[SecurityGroupAssignmentsForAllItemsGet] AS
SELECT * FROM SecurityAssignment Assignments, SecurityGroups Groups
WHERE
Assignments.GroupId = Groups.GroupId
ORDER BY
ItemId, Groups.GroupId

--to:

ALTER PROCEDURE [dbo].[SecurityGroupAssignmentsForAllItemsGet] AS
SELECT * FROM SecurityAssignment Assignments
LEFT JOIN SecurityGroups Groups
ON Assignments.GroupId = Groups.GroupId
ORDER BY
Assignments.ItemId, Groups.GroupId



Best regards,

Simon
Reply
#2
Hi Simon,

I can't evaluate that assessment since I'm not so deep in SQL and I don't understand the impact of that for functionality, but I could imagine that the wizard simply cant understand the data structure we use. But thats only an assumption - I'm really not the correct person here, so please be patient until our ressources will be back after vacation time to have a look at this.

best regards,
Michael
-- michael.scholz@asg.com --
Reply
#3
Why should we change it??? ntext tp nvarchar(max) - could make sense, but I don't think that it really need to be done

And the StoedProc is also working as it is...
Regards/Gruss
Oliver
Reply




Users browsing this thread: 1 Guest(s)