Comments
Sort by recent activity
Hi Tilman.
Another question.
I was using QA, using a specific login user (windows login).
Then, for a specific reason, I needed to open a second window, in the same server/database, but using another sql login.
SPv3 than started getting the schema again. The same schema I think.
I'm presuming you are not checking the permissions wich user have in database (I tested this, SPv3 bring me a table in intelissense that my user don't have permission). So, why is it necessary do get the schema again?
Another question, is, maybe can be a good idea, when opening a new widow, a dialog box asking if the user want's to use intelissense in this windows. I think in SQL Prompt 2 it's work.
In the sample above, I needed to disable SPv3 and open a new QA application with the second user.
Thanks
Ésio Nunes / comments
Hi Tilman.
Another question.
I was using QA, using a specific login user (windows login).
Then, for a specific reason, I needed to open a second window, in the same server/database, but using anoth...
Hi Tilman.
I'm sorry, I didn't undestand "schema panel". Is this QA Object Browser?
If it is; yes I can my schema information there.
Regards,
Ésio / comments
Hi Tilman.
I'm sorry, I didn't undestand "schema panel". Is this QA Object Browser?
If it is; yes I can my schema information there.
Regards,
Ésio
More details.
Today morning I started QA, and all worked fine. I one of my initial windows I type some alter procs statements.
During the day I opened other windows (not too much, only 3 or for, and always closing unused windows, please see this topic http://www.red-gate.com/messageboard/viewtopic.php?t=3884&highlight=).
In some moment, in one of my older windows (that I used typing different statments and deleting these, to reuse the connection), I type again alter proc and ... SPv3 brings me the message "...cannot be scripted. The object may be encrypted.". But I used this window to edit these procs earlier!!!! And now it isn't working.
No problem, I opened a new window, for brief moments I watched the message about SPv3 get the snapshots (from the memory I think) because I'm using the same database I used in oldier window.
I typed the alter proc, and this time, it's worked, SPv3 brings me the proc code, BUT, it brings me the original code, not the code I changed in the morning. I confirmed with one sp_help and the code is changed in database. There is no other person editing my procs. So, SPv3 bring the code from another place other than database? Is from memory or cache? In the topic I mentioned, it was explained the procs text aren't in cache.
Any ideia?
Thanks
Ésio Nunes / comments
More details.
Today morning I started QA, and all worked fine. I one of my initial windows I type some alter procs statements.
During the day I opened other windows (not too much, only 3 or for, an...
Complementing
Are my procs/functions source code stored in memory? What happens if:
I open my QA -> SPv3 reads my database schema.
Anoter user change one proc souce
I use alter proc -> SPv3 get the source from memory, or it go back in database to get the fresh source?
Thanks
Ésio Nunes / comments
Complementing
Are my procs/functions source code stored in memory? What happens if:
I open my QA -> SPv3 reads my database schema.
Anoter user change one proc souce
I use alter proc -> SPv3 get the...
Hi Tilman
This values '450 mb im swap' I catch in Task Manager in column: Virtual Memory Size.
And I picked these memory values from Task Manager now, for your information:
Begin
1 - I minimized my QA yesterday nigth (with 8 windows), and still doesn't started working with this until now, I have these values: Memory Usage 28MB and Virtual Memory Size : 497MB.
2 - I maximized QA and starting a new window (9 in total now), the values growed: 231MB Memory Usage, 699MG Virtual Memory
3 - I closed 7 windows, the values didn't shrink a lot.
End
My machine has 1GB RAM, so it's not a bad physical memory value.
I understand the memory SPv3 is using, is of course used to build the lists, but you must agree with me that 699MB RAM is a high value, and we need to consider I'm not opening only QA in my station. As I mentioned, I'm testing in a real production environment, with all task I do every day.
About blocking some databases, I'm alredy done this, I'm using only that I really need. Maybe it be a good ideia, the system database come blocked by default... They are small, but maybe this helps.
I understand SPv3 uses memory to do its job, but maybe it will be a good idea review this memory consumption use. I don't understand why it uses different candidate list for each query window, if that distinct windows use the same database/credentials.
Thanks a lot
Ésio Nunes / comments
Hi Tilman
This values '450 mb im swap' I catch in Task Manager in column: Virtual Memory Size.
And I picked these memory values from Task Manager now, for your information:
Begin
1 - I minimized m...
It brings me another question.
Probably SPv3 is getting into your memory, the "source" from all my objects, including all my procs. For my databases, I had a lot of procs, certainly the procs scripts are consuming most momory than tables objects.
Maybe it be a good ideia, in the first moment, when SPv3 gets the database schema, get only my procs names and parameters. If I use the command alter procs.. then SPv3 get the proc source.
Thanks / comments
It brings me another question.
Probably SPv3 is getting into your memory, the "source" from all my objects, including all my procs. For my databases, I had a lot of procs, certainly the procs scrip...
I'm getting same problem.
I had deleted that file, and didn't worked too.
Ésio / comments
I'm getting same problem.
I had deleted that file, and didn't worked too.
Ésio
Yes I had the previous beta verions (SQL 3), and too SQL 2. But I had desintaled both before trying this beta.
I tried renaming that file, according your suggestion, but it doesn't worked.
So, I removed alll SQL Prompt 3 directory in Application Data, and Bingo, it' working now.
Thanks
Esio Nunes / comments
Yes I had the previous beta verions (SQL 3), and too SQL 2. But I had desintaled both before trying this beta.
I tried renaming that file, according your suggestion, but it doesn't worked.
So, I re...
Hello, it's:
All my servers is running on Windows Server in English.
Portuguese is only to client machines.
Sql Server Version
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
Standard Edition 8.00.2039 SP4 / comments
Hello, it's:
All my servers is running on Windows Server in English.
Portuguese is only to client machines.
Sql Server Version
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:3...