We are working on C++ in eVC++ 3.0 environment (CE 3.0) with SQL CE 2.0.
While executing the SQL CE commands like GetData(),GetNextRows() and Seek(), 8 KB keeps increasing each time in the memory. We are releasing the accessors,columnsinfo,rowsetchange,rowset handles properly.But still the memory increases without being released.
Have we missed out anything?
Kindly help us in this regard.
I am using SQL Server 2000 SE. When I used my application, the SQL server memory go on increasing & it will never come down. Application runs very slowly. Can anybody suggest how to release memory from sql server.
Hi,I am having an issue with SQL server that slows everything to a crawl,and makes almost any query impossible to complete.Here are the symptoms:I stop SQL, I start SQL. The task manager shows SQL starting up andquickly allocates 50 MB of memory. I then open SQL Manager and I canopen up the instance of SQL Server and I expand to see all of thedatabases, memory rises to about 70MB allocated. I then expand adatabase and view a list of tables. The memory allocation quicklyrockets to 860+ MB and any attempt to query they database results inhuge hang times.I have MacAfee anti-virus in place and it is constantly scanning forviruses, so I don't think it is a virus. The log files do not appearto be large. I have done everything I know to do to resolve this. Anyhelp would be much appreciated.Does anyone have any ideas?Thank you for taking the time to read this.Tod
I have developed my web application using ASP.Net with MS SQL SERVER Express Edition SP2 . I have hosting it at some where which i can remote and see the service of sqlservr.exe . The first start of this service take the memory space just only 25 MB but after this service run upto one week it increased up to 200MB .This service won't realease from the memory untill unless i restart the server or restart its service.
1.Could any one tell me why this service continue increasingly ?. 2.What can i configure in MS SQL SERVER 2005 EXPRESS Edition to let this release from the memory without restart the server or its service ?.
I've tried searching for details on the next release date of SSRS, but can't find any. Has anyone heard anything regarding the next release? There are at least a dozen features that I really would like to have, and when searching for each, the MSFT developer typically responds with "that feature is targeted for a future release". So I'd like to know if anyone has any idea, even heard a rumor, regarding the next release timeline. Or, is there a better place to search for this information?
Hello. I have received the follwoing error upon an attempt to Browse the Cube. All other tabs are functional, including the Calculations tab. We are running Windows Server 2003 SP2 and SQL Server 2005 SP2. Any suggestions would be greatly appreciated!
**EDIT** - Have confirmed SP1 for VS2005 is installed both locally and on server, also.
Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (Microsoft Visual Studio)
------------------------------ Program Location:
at Microsoft.Office.Interop.Owc11.PivotView.get_FieldSets() at Microsoft.AnalysisServices.Controls.PivotTableFontAdjustor.TransformFonts(Font font) at Microsoft.AnalysisServices.Browse.CubeBrowser.UpdatePivotTable(Boolean translate) at Microsoft.AnalysisServices.Browse.CubeBrowser.UpdateAll(Boolean translate) at Microsoft.AnalysisServices.Browse.CubeBrowser.InitialUpdate() at Microsoft.AnalysisServices.Browse.CubeBrowser.SupportFunctionWhichCanFail(FunctionWhichCanFail function)
I've been researching AWE to determine if we should enable this for our environment.
Currently we have a quad core box with 4 gb of RAM (VMware). OS: Windows 2003 std, SQL Server 2005 std. 3GB is not set but will be as soon as we can perform maintenance on the server.
I have read mixed feedback on AWE, either it works great or grinds you to a hault. I would assume that the grinding to a hault is due to not setting the min/max values correctly or not enabling the lock page in memory setting.
We only have one instance of SQL on the server and this box won't be used for anything else aside from hosting SQL services. We do plan on running SSRS off of this server as well.
1. Will running SSRS and enabling AWE cause me problems? Will I have to reduce the max setting by the SSRS memory usage or will it share and play nice?
2. How do I go about setting the Max value? Should it be less than the physical RAM in the box? Right now its set to the default of 214748364, even if I don't enable AWE should this default value be changed?
3. It seems that even at idle the SQL server holds a lot of memory and the page file grows. If I restart the process in the morning, memory usage in taskmon is at 600mb or so. By the end of the day, its up around 2gb. How can I track down whats causing this, should this even concern me?
4. The lock Page in memory setting worries me. Everything I've read on this seems to give a warning about serious OS and other program support degradation. In some cases to the point where they have to restore the settings on the server before they can bring it back up. What are your thoughts on this.
If we upgrade an instance to SP2 (CTP), can we simply apply SP2 (Release) on top of the SP2 (CTP)? Or will we need to uninstall the whole instance, re-install SQL 2005 and only then apply SP2 (Release)?
I notice in section "1.1 Overview of SQL Server 2005 SP2 Installation" of the documentation the statement:
"During installation, SQL Server 2005 SP2 Setup will list all installed components of SQL Server 2005 and allow you to select the components to upgrade, including components that have already been upgraded to SP2. For more information, see the SP2 Setup documentation."
I'm hoping that this means you can apply the release SP2 on top of a ctp SP2 with the result being full release SP2 versions. I've read the "SP2 Setup documentaiton" and it did not clarify for me.
Thanks!
Bob Hodgman
P.S. - sorry for the duplicate posting... I think posting this as a reply to the announcement (as I originally did) didn't get it much attention.
We alter the database schema that our production application uses with almost every release. Is there a way to basically remove the replication and re-do it for all tables / views at one time? Then we could just "rebuild" the replication with every release. We have about 200 tables and 200 views that have many dependencies. I'm sure it could be done with scripting and the stored procedures, but I'm new at this and not sure where to start. Any ideas? Thanks!
I have a Windows sever 2012 with sql server 2012 enterprise. Ram size is 22GB. Sometimes SQL sever takes 95% memory.My question, How to reduce memory size without killing any process because it's production server.So there are many background process is running. And,Is there any guides to learn why Memory is raise d so high and how to reduce it.
I`ve been following the newsgroups, and the consensus had seemed to be that 7.0 would be released around November. However, I spoke to a Microsoft partner last week who told me that the release date would be sometime in the second quarter of 1999. Does anyone know whether if this is true/untrue?
The former programmer wrote this stored procedure. It haven't been run for a while, so I was given the assignment to get it working. When I ran the stored procedure, it took almost 9 hours. Then I found that I can't access a few tables, so my guess it there is some issues with table locking. The stored procedure use this...
Code:
BEGIN TRAN
--blah blah
COMMIT TRAN
ERROR_HANDLER:
ROLLBACK TRAN
Obviously there seem to be a logic error in the middle of the script while running the stored procedure. So, how do I cancel the transaction and unlock the table? I'm unable to access the few tables.
Also, does rebooting the computer helped to release the transaction or table locking?
Hi,Our DBA group is debating production release methodology. We alwaysperfect our deployment package (typically a script) against thedatabase in a Staging environment, before executing the packageagainst Production. One side argues that the safest approach is tocreate a script containing all schema changes, data changes, storedprocs, functions, etc. Run that script against Staging until it iserror-free. Then, when you run it against Production on Release Nightyou know it will also be error-free, since Staging is a copy ofProduction. However, any changes to the deployment, such as updatesto procs (and there are always a bunch in the pre-deployment period)must be manually implemented on the script.The other side wants to take advantage of the .NET environment. Wekeep all procs, views, and functions in a Release folder on VSS,execute a Get Latest Version (Recursive) from VisualStudio, and runagainst Staging/Production. Any changes to the procs areautomatically propagated from VSS to VS, and there is no manualediting of the script. You still need a script for table and datachanges. The "script everything" side of the debate feels this methodis not as reliable, especially since when views are nested, you willget compile errors and must execute the run-on several times until allthe views compile. The "script" side feels that any errors areunacceptable in a Production environment.What is the opinion out there?Thanks!
We have a product that uses SQL Express that is ready and waiting to go to market. It absolutely requires Vista compatibility on day one. When will SP2 be released? The UAC problem has been known for months.
We cannot distribute the November CTP, of course. Manually correcting SQL Express installs on Vista using the recommended workaround is impractical to say the least.
Is there a way to tell what release of SQL Server 2005 is installed without the management studio? I was working on a server with SQL 2005 installed, but I wasn't sure if it was full or express. The person who installed SQL didn't include the management studio. Thanks in advance.
I downloaded Sql server 2008 Nov CTP and am gonna use that. Just wanna make sure if I can migrate from this version to the release version? Coz the release won't come till the end of next year (?!) so...
I have extracted the files from the Microsoft download and am all ready to run SETUP for the MSDE 2000 release A for Visual Studio .NET 2003 Pro.
Is there anything I need to know about or run or configure for it all to work?? I am a newbee and I am the only user on my XP Pro machine under Administrator.
Hi all, I'm running SQL 7.0. Due to large tables, the space on the SQL server was getting filled up. So i truncated some tables. Now even though the SQL dbase shows 3Gb free, the HDD shows only 150 MB free. How do i get SQL 7.0 to release the sapce back to HDD?
I am doing an upgrade of SQL Server from Beta 3 release to the release version. I will appreciate if I get some information , some tips that I should follow which will make my task simpler. The database is very critical and big. It has huge amounts of stored procedures. If you can tell me any site which gives information regarding this that will be also helpful..
does anybody know when SQL Server 2005 Service Pack 3 will be released?
We are currently encountering a lot of problems with replication. We have seen that the different SP2 Cumulative Updates are fixing a lot of replication troubles... but as they are not fully tested, we do not want to install them on our production servers.
MSDE 2000 Release A installed under windows 2000 pro will notcommunicate with SQL Server Manager nor MS Access on peer computer.Can someone help?Have set DISABLENETWORKPROTOCOLS=0 at install time.Install log shows installation successful..Control Panel> Admin Tools> Services section shows SQL server instancerunning.Disabling firewall has no effect.SQL Server Manager (icon at bottom right in task tray - thisstarts/stops Server instances), on same computer as SQL Serverinstance, shows only instance "H" which is the same as the computername. (This instance was uninstalled before new instance wasinstalled.) Typing new instance name ("HABC" and variations) intotop combo box produces error messages such as "wrong format for name","Network path not found" "RPC service not running". What is thecorrect computer/name format?? Key problem is clearly that ServiceManager can't communicate with this local MSDE instance.All Windows 2000 updates from MS web site have been installed.Objective is to operate MS Access on computer X (also running Win 2000Pro) with computer H as a peer that hosts MSDE.Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??---Mark Ferguson
does anybody know when SQL Server 2005 Service Pack 3 will be released?
We are currently encountering a lot of problems with replication. We have seen that the different SP2 Cumulative Updates are fixing a lot of replication troubles... but as they are not fully tested, we do not want to install them on our production servers.
When -all- records from a table with a varbinary(max) column are deleted (not via truncate), the table properties still show a dataspace size from before the delete operation. Inserting new blob records only leads in the growth of the allocated space withouth reusing the empty already allocated space.
Runnning commands like dbcc updatusage/checkdb/cleantable/reindex or sp_spaceused @updateusage = N'TRUE' seem to have no effect.
Does anyone know when space allocated by a varbinary col. is released?
thanks, Derk
running SQL 2005 STD ed SP2. DB is in simple recovery mode.