How to increase the SQL Server memory

We are using SQL server 7.0, our users use to connect to SQL server remotely using Visual Basic Application. When all the users are connected it keeps on increasing the memory utilization and at 1,836,848 KB memory utilization it stops increasing the memory i.e memory utilization become stangnet. The actual amount of physical Memory is around 5GB but SQL server dont increase it after the treshhold level and the performance of the server get affected badly. Any one please suggest me the possible solution.In Enterprise Manager,
- right click on the server name and choose properties.
- choose memory tab

You should be able to set your min/max memory settings there. Also look into worker threads (on the processor tab).

Something else to think about,
How big is the DB (Gigs) ? How big are the tables being referenced? Perhaps something could be re-designed to make things more efficient. Are there a lot of table scans where you could have indexes, etc..?

Also,
Open the performance moniter and check the sql counters..

More info at -> http://www.sql-server-performance.com/performance_monitor_tips.asp|||It looks like you're running Standard Edition of SQL2K, which will not recognize any more memory, period! You need to upgrade to Enterprise and then you'll have more options:

1. /3GB in boot.ini will allow SQL Server to use more than the default 2GB
2. /PAE in boot.ini and enabling AWE on SQL Server will give SQL service whatever amount you specify.

How to Import Data from AS400 files to Sql 2005 tables?

Hi All,

I want to Import data from AS400 to Sql2005. From the Sql Management studio I invoke the Import Data wizard. For the source I connect to the ISereis system and for the Destination I select the Sql2005 Database , When I go to the next step i.e select source tables I get the error
"An error has occured which the SQL Server Integration Wizard was not prepared to handle
No error message available,result codeB_E_CANTCANCEL(0*80040E15).(System.Data)" .After this I am unable to proceed further. I am using client Access tool to connect to ISereis

IBM DB2 UDB for isereis IBMDA400 OLE DB Provider

Regds,

Anu

If this is going to be a regular task, might as well dump your AS400 data in a delimited text file and import from there|||Moving to the SSIS forums

How to i get all the data from database within CD?

In my company i have one requirement.i have a database in sql server and i
have one report generation application to connect that database an it will
generate reports.for this client machine must have sql server.now my client
need data and application in one cd .he want to see the reports using that
cd.without sql server how can we access that database.is it possible ?
hi,
MOHAMED NASEER wrote:
> In my company i have one requirement.i have a database in sql server
> and i have one report generation application to connect that database
> an it will generate reports.for this client machine must have sql
> server.now my client need data and application in one cd .he want to
> see the reports using that cd.without sql server how can we access
> that database.is it possible ?
you can put a SQL Server/MSDE database on a CD (the like, as later
explained), but SQL Server/MSDE must be present and installed on the target
pc in order to acces that database and related data..
storing a database on CD support can be performed using sp_create_removable
system stored procedure, but this will always produce a 3 files set database
at least...
1 file storing the actual database data (that can be stored on the CD
support)
1 file for the transaction log (that can be stored on the CD support)
1 file for system tables that must stored in a read/write hosting area...
usually the targed pc hard disk..
the database will be of course a readonly database but a part of it, the
data file storing the system tables, must of course be read/write in order
to allow security features like granting database access rights and
permissions..
that's to say, a database can not be totally self contained in a CD-ROM and
more, before using it, it must be attached on to the target database via
sp_attach_db system stored procedure and detached via sp_detach_db before
ejecting the CD (the database will be marked as suspect as unavailable if
the detach operation is skipped)
further info about the sp_create_removable stored procedure and related
synopsis can be found at
http://msdn.microsoft.com/library/de...es_03_92hx.asp
and
http://msdn.microsoft.com/library/de...ca-cz_2e79.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply