Hi, i'd like to try Express2005 but before i'd like to know wich are the limit vs Sql Server. I had seek in Microsoft's site but i haven't found it anyone kwon it ? Thank's for the answer
I've been developing a vb app with sql server 2005 and had planned to use express as the client server so the db could be distributed with the app. After importing 21 csv text files, I realized that I have way too much data. My understanding is that sqlexpress can only work with max 4gb database.
The 21 csv files (total 925mb) brought the db size up to 1.5gb and I still have at least 250 more files to go. Obviously, I need a different approach. What are the size limitations of the non express version of sql server 2005? Any suggestions on the best approach for this type of situation?
I have 1 problem here. I developed a desktop application and I am using SQL 2005 Express as my application database.
I found that after I closed my application, the SQL 2005 Express memory resources do not release. How do I release the memory resources except of restart the SQL services?
Do you guy have any better recommendation of other database is more suitable for desktop application?
SQL Express Ed is limited to one CPU, what happens if the CPU is a dual core CPU? Does SQL Express care? Does it see a dual core as a single CPU?
As for memory, stupid question, SQL Express is limited to 1 GB RAM, if I run it on a server with say 4GB of ram packed into it, will it affect SQL Express' performance? Will SQL Express even run if there is more than 1GB available? Or will SQL Express simply ignore the extra RAM with no negative consequences?
I'm hoping that some might have an answer for me after much net searching.
I have a server (200GB disk space, Dual 3.8 GHZ processors, 4GB memory) that hosts 6, very small, SharePoint sites (WSS 2.0) and SQL 2005 express handling 1 config DB and 7 content DB's. The biggest DB at the moment is only 300 MB and the sites are not actively being used yet, they are only open to a select number of users (+ - 25 in total) who are using them as reference "areas" at the moment. Each site is running in it's own application pool as well.
I find that the sqlserv.exe process increases in memory usage and does not seem to decrease. It gets to the point of 960 MB usage and then databases cannot be used (SQL 2005 Express max memory is 1GB). SQL seems to "close" them down and site errors being received are "site is not in configuration database". When the SQL service is restarted the memory usage idles around 70 - 80 MB, the sites are 100% again but after an hour or 2 the memory usage is sitting at 560 MB again and doesn't seem to decrease.
Is there a way I can bring this memory usage down?
AM I correct that with a quad box running sql server 2000 enterprise edition running on windows 2003 enterprise edition, I can put 32 gig of memory which sql server can use. Need response ASAP, Thanks
I am migrating a data warehouse from SQL 2000 to 2005. So far, I have been able to convert all DTS's on the old server and most tables and users. I am having problems with some of my views, though. A view which involves over 5 tables, and some sub-views of those tables runs perfectly on SQL 2000, but on 2005 I get a Query Timed out Message. A typical run of this view can return from 200-1000 records. My guess is that it gets stuck somewhere in the subviews it has to run. So I wonder, what are the limitations of SQL 2005 concerning Queries and sub-queries (how many subqueries can a query have without timing out?). I mean, I would expect 2005 to have more processing capacity than SQL 2000 (on which this query runs perfectly). I have run some queries which don't run on 2000 but do run on 2005 and return over 4000 records.
Or is there some setting I haven't adjusted, like the time it takes for a query to time out? How would I adjust this, then?
I am in the process of testing a SQL 2005 Std x64 server with merge replication using Windows Mobile 5.0 clients and SQL 2005 Mobile. The test DB is a copy of the currently active DB, but has been expanded to include some new tables to support planned application functionality extensions.
Once the publication exceeds 97 Articles, the error is thrown that "The buffer pool is too small or there are too many open cursors". If I drop one article everything is fine. I ran a test with dummy DB that had 100 blank tables, and this initialized just fine on the client. The additional articles I am publishing (the 98th table) is also empty, but it throws the error anyway.
Is there a limit on the total size/number of changes that can be sent? Since I have run tests sending over 64,000 changes to a client during initialization this does not seem to be the case (I am only attempting a little more than 9,700 changes on this initialization).
Some other ideas that have been tested without success are to stop the user triggers from propagating, and toggling the AWE setting for SQL. The Replication Monitor does say the client completes replication, and it seems to choke at the very end of completing replication when it attempts to write to the tracking tables. The last successful action is sys.sp_MSadd_merge_history90, and it appears to be acting on the last table added to the publication.
There does not appear to be a limit on the number or articles, since I can publish more articles in a dummy DB than I am able here, so it seems to be something to do with size. Any information would be helpful, this is a very frustrating issue. Thanks!
I'm trying to learn some VB programming with the VB 2005 Express Absolute Beginner Series video tutorials (which I think is great) and have come across a problem that I can't solve.
When I follow the instructions in Lesson 9 (Databinding Data to User Interface Controls) my application will display the data from the database correctly and I can edit it (and as long as the debugger is running the data remains changed). However, the changes won't propagate back to the database. I don't get any error messages but after I edit the data, save (with the save button on the BindingNavigator toolbar), and end debugging the data in my database remains unchanged. When I use a MessageBox to show how many rows where edited/updated in the
I get the correct number back. I'm sure the problem is not due to coding errors since I've also tried running the accompanying Lesson 9 project file that can be downloaded from MSDN and the problem persists.
I'm using Windows XP SP2, SQL Server 2005 Express Edition and VB 2005 Express Edition. I've tried installing SQL Server 2005 Express with a number of different settings, including default settings, but it doesn't make any difference.
Would greatly appreciate any feedback on this as I'm keen to resolve this problem so I can get on with the next tutorial lesson.
We are developing some applications for Sunit computers (In-vehicle computers) which have limited memory . Because the applications display maps, the will consume alot of memory. Because of this, we want to restrict the amount of memory and other resources SQL Server Express uses to a minimum. I've tried setting 'max server memory', which doesn't help too much as this is only a limit on the SQL engine and not the sqlserver.exe process. What other settings and restrictions can I apply to limit memory consumption by the process?
We have considered using SQL Server Everywhere, but as it doesn't support ODBC (will there be any ODBC support?), we are not too happy about using it. As of now, we have no experience with OLE DB, and the application is MFC 6.0 so we can't take advantage of ADO.NET
I am aware that SQL Express has a memory limitation of 1GB. I am trying to determine if this 1GB memory is shared with the Report Server. In other words, if I run a query that requires 600MB of memory, and a report that pushes the Report Server to 600MB of memory, will I exceed the 1GB limit for SQL Express? Or are these two separate processes for memory limitation purposes?
If they are separate processes, are there any limitations to the Report Server as far as performance when using the Express edition of SSRS? If not, would it not make sense to push the Report Server harder than the database when running reports if SQL Express is my target platform? (e.g., do MORE work in the RS, and less in the database itself)
HiIm trying to connect Visual Basic Express 2005 to a remote SQL Server Express 2005. I cant find how i can do that in VB.net Express.In Web developer there are no problem to connect to a remote SQL server but i cant find it in VB.net Express. The XP with the SQL server that i want to connect to is on the local network. Greatful for help!
This problem only occurs after deployment, not when debugging. In the table I am having a problem with I have an ID field designated as the primary key with the identity increment set to 1 and the identity seed set to 1. There is no data in the table when deployed. I can add records to the datagridview control but when I try updating the dataset I get this error indicating that the ID field already has a value of 1 present. If I close the application and re-start it, the exception no longer occurrs when I update the dataset. I am including the code to update the tables incase something is wrong there. Any suggestions?
Hi Guys, I created a Product database table using Visual Basic 2005 Express and SQL Server 2005 Express. I have just added a new column [Picture] to the database table, which of course, should store an image or picture of a product. I am writing to kindly ask you guys for help .
i) How do I include image files into this column [Picture]? ii) How do I get this image to display on Visual Basic 2005 Express form, so that when a product is selected the product image is displayed accordingly?
When I installed VS 2005, it installed the default version of SQL Server 2005 Express that ships with Visual Studio 2005 installer media.
How can apply SQL Server 2005 Express SP1 to update this existing instance?
Currently, if I run this query:
SELECT @@version
I get the following:
Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
After applying SP1, I should get 9.00.2047.00.
Should I just go to this link and download & install the SQL Server 2005 Express Edition SP1:
I am new here and new to SQL Express. I've searched for my issue, but can 't quite find anything close to the problem or how to solve it, if it's even solvable. I am using SQL Express on a pc to connect to the back end of a database. The front end application (an access runtime) also runs on the same pc. This pc is on a domain. I think I've tried every combination of protocols, and although connectivity via ODBC is successful, the application can't connect - gives the "server doesn't exist or access denied". When I log on to this computer with the "machine" logon (not the domain), I have SQL Express configured to use shared memory, the application runs just fine. I need to use this database for testing in a non productivity environment, but I really hate to log off the domain to run it. Ideas?
My Sql express will use up to 1G or more memory and never release. I had the same problem on SQL 2005 standard, I solved by adding /3G in boot.ini and turn on AWE. but it seems SQL express doesn;t support AWE. so how could I do here?
1. Installed VB.NET IDE 2008 and SQL Server Compact 2005. IDE requires upgrade of database to 3.0 version which I allowed it to do. After the database was upgraded, I did an amount of coding work in the IDE and then tried to go back to do more database work in SQL. However the database then could not be opened in SQL Server Compact 2005. An error said that because it had been upgraded, it could not be read. It was requiring me to run 'upgrade.exe'. I had no idea what this meant and could find no upgrade available online. 2. Removed VB.NET IDE 2008 and installed 2005 instead. However, the file extension on the SQL Server Compact database is .sdf, but the IDE is requiring a .mdf extension. I have tried everything I can think of to get it to save or to have the desired extension, but I cannot.
Questions:
1. Do SQL Express 2005 and VB Studio Express 2008 work together? 2. If so, how?
It seems as though application each requires a different version of the database. If the database is usable in one, it is not usable in another.
I have a 2005 Express DB I wish to attach to using the 2005 Mgt Studio Client (Not the express version, but the full blown 2005 Mgt Studio Client from the SQL 2005 Standard Edition Install disk). Can this be done, or can I only use the 2005 Mgt Studio Express Edition Client?
I have a 2GHZ cpu with 1GB of RAM. I occassionally see very slow (long) queries against a local SQL Server 2005 Express (SP2) database. The issue occurs against different SQL Queries, but all queries are rather basic select statements Perfmon shows that the SQL Server counter for the "MEMORY GRANT QUEUE WAIT Avg MS" gets extremely high (25000+ ms). Perfmon also also shows that PAGING is not occuring, and the system is not under unsual stress. The problem is not reproducible with MSDE.
Has anyone seen this issue, or have any recommendations for a next course of action?
Hi I am using SQL 2005 64 Enterprise edition with 30GB memory. I have allowed SQL to use min 0 memory and maximum 20GB but sql is only showing it can use 100MB of memory
If i have been using sql server 2005 express for developing my application and i decide to upgrade to sql server 2005 express with advanced services while still working on the same application, what will happen to my application's database. Can i be able to continue with my work with out any major regrets.
* Windows 2003 32bit Enterprise with 10gb RAM * SQL 2005 32bit Enterprise * boot.ini - have added /3GB /PAE switches * Confirmed which account SQL Server is running under and added that account to Local Policies/User Rights Assignment/Lock pages in memory * Enabled AWE in SQL SERVER * set minimum and maximum server memory to 9gb * Rebooted.
Task manager says the following: sqlservr.exe - 95MB usage * I know this is normal when using AWE right? The actual physical memory used is 3.13GB and never goes higher. So this leads to believe that SQL is utilizing 3GB because of the /3GB switch, but it's not using the rest like it should be. I tried it without the /3GB switch and it only went up to about 2.1GB usage.
I've turned on performance monitor and SQL server target memory says 8.65 GB while the Total Server Memory says 2.45GB.
I've run: EXEC sp_configure 'show advanced options' RECONFIGURE GO
EXEC sp_configure 'awe enabled' RECONFIGURE GO
And it confirms that the running value for both is 1
My organization is currently migrating about 35 databases from SQL 2000 to SQL 2005. Most of the databases are small with the largest being about 6gb. These databases are not very transaction intensive. We are about half way through as we started the project a year ago. We purchased new hardware for this SQL 2005 so it is a side-by-side migration and it has been going well so far. I made one oversight which I think will come back to haunt us down the line. I installed Windows Server 2003 Standard R2 Edition and of course now I am considering putting more RAM in the server. We have 4 GB of RAM in the server and of course Standard Edition will not address more 4GB of physical ram. I have not seen any memory pressure yet but as databases are migrated over the amount of physical RAM drops. My buffer hit cahce ratio and page life expectancy performance counters are fine so far. The server is a brand new HP DL 380 G5 with with tons of disk and processing power, but only 4GB of RAM. I can't migrate to another server with more ram obviously.
1. What would you do in a situation like this?
2. I could do an in-place upgrade to Windows Server 2003 Enterprise R2. Has anyone attempted an in-place upgrade? I have no applications on this server, just SQL 2005 Standard.
3. Would the /3gb switch be an option? I have heard mixed reviews on this one.
As far as database optimization, %75 of the databases are third party so we have little flexibility in tuning them or redesigning tables.
We have been using SQL 2005 for quite sometime however recently I have been seeing memory issues. SQL will grow to use the maximum available! I have set min 1024MB and max to 15360MB leaving approx 5GB for OS.
Windows 2003 64 / SQL2005 64 Lock pages to memory - enabled Min and Max - 1024, 15360 AWE not checked
We have recently added link server using OLEDB DB2 provider. Could this be the issue?