Comments
Sort by recent activity
Hi Bart
No I am not logged in as sa. I use intergrated security. I have admin rights in our sql-server. So, yes I have dbo access.
I am not working cross database, so I uncheck the option you mentioned. And now I have no stops anymore, even if there is dbo. in front of the tablename.
BTW. the same stops happened when a column name is preceeded by its table name (like tabname.columnname) . Unchecking the cross database support also lets the stops go away.
Thanks, your tip helps me a lot
Bye
Michael / comments
Hi Bart
No I am not logged in as sa. I use intergrated security. I have admin rights in our sql-server. So, yes I have dbo access.
I am not working cross database, so I uncheck the option you menti...
Hi Bart
Thanks for your response.
My SQL-script is about 50-70 lines only. When I scroll down and the cursor hits a column name inside a select/insert/update statement, then it stops a short moment. The cpu goes up to 30-35%.
When the cursor hits a table name it stops 3-4 seconds and the cpu has a 15% spike.
After some more testing I found out that when I use table names like dbo.tabname I have the stop. When I remove the dbo. then I can scroll without the stops.
May be this helps you.
My PC: 3GhZ HT CPU, 1GB RAM, Win XP SP2 with all hotfixes and updates via Microsoft update.
Bye
Michael / comments
Hi Bart
Thanks for your response.
My SQL-script is about 50-70 lines only. When I scroll down and the cursor hits a column name inside a select/insert/update statement, then it stops a short moment...
I have the same problem. Also when the cursor enters the name of a colum it gets very slow. When I try to move the cursor one step to the right, left, up or down, I have to wait about 2-4 seconds, each step!
I do not have this problem with the 3.1 version.
Bye
Michael / comments
I have the same problem. Also when the cursor enters the name of a colum it gets very slow. When I try to move the cursor one step to the right, left, up or down, I have to wait about 2-4 seconds, ...