SQL Server 2005 AWE memory allocation

Hi All,
I have a very simple doubt which seems very difficult to find on msdn literature.
This query gives me awe_allocated_kb column and lists all memory resources in SQL Server, right?
SELECT *
FROM sys.dm_os_memory_clerks
Being it a column in a list give me a strong feeling that I can distribute awe memory for different memory buckets, right? All my humble 10485760 kb is allocated to 'MEMORYCLERK_SQLBUFFERPOOL'.
I'd like for instance to add some memory to 'MEMORYCLERK_SQLQUERYEXEC'.
How can I achieve that? It seems to be a simple thing with SQL 2008 resource governor, but I'm lost on SQL 2005.
Thanks a lot in advance.
Lucas

Being it a column in a list give me a strong feeling that I can distribute awe memory for different memory buckets, right? All my humble 10485760 kb is allocated to 'MEMORYCLERK_SQLBUFFERPOOL'.
I'd like for instance to add some memory to 'MEMORYCLERK_SQLQUERYEXEC'.
How can I achieve that? It seems to be a simple thing with SQL 2008 resource governor, but I'm lost on SQL 2005.
Thanks a lot in advance.
Lucas
Hi
No you cannot its system internal behavior and you cannot edit it. Memory clerks are kind of brokers when ever any component needs memory it refers to its respective clerk for it and clerk goes to memory allocators and get memory for them.
AWE memory in 32 bit can only be used by data and index pages
Again MEMORYCLERK_SQLBUFFERPOOL is clerk which is listening to various requests and getting memory for them. They dont have any memory reserved with them which they can give they just act as
middle men and caters to request.
PS: I have replied to your other thread
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

Similar Messages

How much Memory should be allocated to SQL Server 2005

Hi,
I have a SQL Server 2005 installation on a server having 64GBof RAM.
SQL server is allocated 57GB of the available RAM.
Could you please tell me what would be the ideal RAM allocation for my scenario. is the one that is set now, fine.
How much RAM should be left for the OS and other processes to run?
I have around 8 databases on the server and the cumulative size of all the databases in about 800GB, these are highly used servers, used for a public domain.

Umesh,
Saeid and Uri has already given you good articles to refer to please read them. Reg SQL Server utilization I am sure you are referring to task manager which is always not correct place to look for memory utilization. Below link has query which will give
you SQL Server memory utilization
http://blogs.msdn.com/b/sqlsakthi/archive/2011/02/28/t-sql-script-to-monitor-memory-usage-by-sql-server-instance.aspx
Article provided by Uri will give you not absolute value but almost correct value, but since you asked absolute value you need to look at performance counter to reach at correct memory utilization. If you refer to section 'Does my SQL server has low memory'
in article which Saeid gave you will find list of counters to monitor for memory utilization use the counters to reah absolute value.
>>OK, Can high RAM utilization by sql server cause the OS to restart by any chance.
IMO its not possible I have never seen SQL server being cause for OS shutdown. SQL Server works in non preemptive mode and will yield memory to OS when required. One possibility is when SQL server has locked pages in memory(LPIM) and some rouge process
or driver starts using memory from OS heavily and since SQL server memory is locked( due to LPIM privilege) it cannot trim heavily resulting in OS to terminate but this is not because of SQL server but because of bad drivers and processes leaking
memory on OS.
SQL server using memory is normal behavior
>>This question seems vague, but I had to ask this, because my server restarts abruptly and I don't get valid reasons in the Logs for that matter.
Does SQL server starts abruptly or windows OS ? Please look at event viewer for more details and SQL server logs. Is your SQL Server 2005 patched to SP4
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

SQL Server 2005 Memory Explosions

We have the following configuration:
ESXi 5.1.0 running on three clustered Dell 710 servers
vCenter Server 5.1.0
The clustered servers have a total of 88G of RAM
SQL Server 2005 x86 running on a virtual Server 2008 R2 x64. All databases run fine for several days with memory usage seeming at ~25%. Suddenly, the memory consumption
shoots up to ~98% and we have to reboot the server. This is based on information from the task manager and the measurements in vSphere Client. I understand that the task manager is not an accurate measurement when AWE is active but that’s the best I’ve got
at the moment.
Here's what we've done thus far:
Looked through the logs on the SQL Server and found the following:
In the System log, Resource-Exhaustion-Detected appeared at the same time but the highest memory consumption was services.exe at 125MB. Doesn’t seem to be the culprit.
In the Applications log, started getting MSSQLSERVER errors indicating ‘The Server was unable to load the SSL provider needed to login.’ These errors persisted through the downtime.
In the SQL Server Log File Viewer, we see the following errors, though I’m not sure that they are at all related:
A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 0 seconds. Working set (KB): 4464, committed (KB)
66976, memory utilization: 6%
(About 4.5 hours later) Warning: the available page file has dropped below 4Mb. It is at this point – seemingly – that the memory usage has jumped up to near 100%.
The virtual server has 8G of RAM allocated. However, within the vSphere Client, the Memory Granted and the Memory Consumed seem to be at the same value…meaning that
the consumed value seems to be at 100% under normal operating conditions. Not sure why that is.
If anyone has any recommendations or areas to look, we would certainly appreciate your assistance! Thanks in advance.
Tony

I thank you guys so much for the rapid response! Please forgive the delayed response. All of this is on a DoD network and I cannot post to blogs on government machines. I have to go to a private
machine. Below is the information you asked for:
The Max Server Memory is 5.0GB and the Min Server Memory is 0.0GB
I have PerfMon currently running to try and capture as much information as possible.
We are getting a few other errors in the SQL Log that has given me some concern:
Failed Virtual Allocation Bytes: FAIL_VIRTUAL_RESERVE 65536
Memory Manager VM Reserverd = 3673288 KB VM Committed = 55688 KB AWE Allocated = 0 KB Reserved Memory = 1024
KB Reserved Memory In Use = 0 KB
There is also a series of MEMORYCLERK and CACHESTORE errors following
The Server was unable to load the SSL provider needed to login. SSL is used…
o
I presume that this is due to the lack of memory to process these SSL request.
There are indeed several Error: 701, Severity: 17, State: 123
Below is the system information from SQL Server 2005:
Microsoft SQL Server Management Studio                   9.00.5324.00
Microsoft Analysis Services Client Tools                       2005.090.5324.00
Microsoft Data Access Components (MDAC)                6.1.7601.17514 (win7sp1_rtm.101119-1850)
Microsoft MSXML
            3.0 6.0
Microsoft Internet Explorer
8.0.7601.17514
Microsoft .NET Framework
2.0.50727.5477
Operating System
            6.1.7601
I run a query SELECT SERVERPROPERTY(‘edition’); and it shows ‘Standard Edition’ rather than ‘Standard Edition (64-bit).’
We are using Windows Server 2008 R2. I don’t believe that there was an x86 version released but I could be wrong.
I’ve actually looked at enabling the LPIM but we are on a domain that we have no control over and there are GPOs that make it very difficult if not impossible to gpedit but that is something
we can certainly look into with the domain owners if you think it might help.
I just ran the following script in SQL:
Exec sp_configure ‘AWE’
The response is name – awe enabled, minimum – 0, maximum – 1, config_value – 0, run_value – 0
There is no third party software on this server.
The Max Server Memory is set to 5GM
Again, I do appreciate all of your help. Please let me know if I can provide anything further.
Tony

Sql server is using memory more then there max memory setting?

Hi All,
today i have faced the different issue..........
we have one SQl server 2008 prod server... it have memory issue actually total server memory is 8GB and we have allocated the 6 GB to SQL server,we checked the server no open trans and dont have running jobs also,one database is using the memory high(no
open trans)... but Sql server has used 6.5 GB (6 GB) and total server used memory is reached to 7.89 GB.
Please tell me how to find the most costly query in particular database wise and sql server internally behavior ?
how to troubleshot the above issue?
please post the your valuable answers ASAP...
Thanks,
RAM

Please refer to what Olaf said briefly.Buffer pool in SQL server only caters to memory requests which requires pages <8 KB . Almost all requests are satisfies by buffer pool and generally request for memory is small and so buffer pool satisfies the requests.
However there are some direct memory allocation by windows API which is done by windows for requests which requires memory greater than 8 KB. This memory wont come from buffer pool and this would be counted in memory utilized by SQL server. SQL
CLR,XML, linked Server, all takes memory outside buffer pool in SQL Server 2008. This behavior changed in 2012 so my statement only applies to SQL server 2005/2008 and 2008 R2.
I would run below to check SQL server memory utilization.
select
(physical_memory_in_use_kb/1024)Memory_usedby_Sqlserver_MB,
(locked_page_allocations_kb/1024 )Locked_pages_used_Sqlserver_MB,
(total_virtual_address_space_kb/1024 )Total_VAS_in_MB,
process_physical_memory_low,
process_virtual_memory_low
from sys. dm_os_process_memory
I am sure you must be using some features mentioned above.You were worried that even though there is no query running on SQL server it has still holded up the memory. This is default behavior and this is how memory management in SQL Server works. It will
not release memory untill SQLOS asks it to do so which is told by windows OS thorugh some flag that it is facing memory pressure.
Please read below for more details on memory. There is section to test whether system is facing memory crunch please read that as well.
http://social.technet.microsoft.com/wiki/contents/articles/22316.sql-server-memory-and-troubleshooting.aspx
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Problem with netbeans 5.5 + sun app server 9 + ms sql server 2005 + datadir

hi ,
i am having new netbeans 5.5 beta with sun java application server 9 and microsoft sql server 2005 , my question is simple whats is the correct procedur to retrive schema and table and generate ejb etc... adn to update data base using
datadirect . bcos whatever i do it is giving me this error
Deploying application in domain failed; Deployment Error --
Internal Exception: java.sql.SQLException: Error in allocating a connection. Cause: Class name is wrong or classpath is not set for : com.ddtek.jdbcx.sqlserver.SQLServerDataSourceError Code: 0
C:\Documents and Settings\chirantan\WebApplication4\nbproject\build-impl.xml:437: Deployment error:
The module has not been deployed.
See the server log for details.

Hi,
I have installed J2EE 5 SDK on windows XP. When I installed NetBeans 5.5.1 and tried to register it with Application Server, it got registered automatically. I had to uninstall both due to some reasons, now when I installed both j2ee and netbeans again, i see D:/Sun/AppServer folder empty and not able to register NetBeans 5.5.1 with application server. I tried again and again by reintalling but AppServer folder remains empty and not able to register. Any help for this issue??????????

SQL Server 2005 SP2 install on Vista

Hi,
I have all updates for Vista, tried to install SQL Server 2005 SP2, the following log file:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version      : Professional (Build 6000)
Time            : Wed Mar 26 12:20:54 2008
USER-PC : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
Machine         : USER-PC
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLSupport_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLNCLI_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SqlWriter_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLSupport_2.log
Machine         : USER-PC
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLNCLI_2.log
Machine         : USER-PC
Product         : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQL.log
Machine         : USER-PC
Product         : Workstation Components, Books Online and Development Tools
Warning         : Warning 28123.Warning: SQL Server Setup cannot install this feature because a different edition of this feature is already installed. For more information, see 'Version and Edition Upgrades' in SQL Server Books Online.
Machine         : USER-PC
Product         : Microsoft SQL Server 2005 Tools Express Edition
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_Tools.log
Setup succeeded with the installation, inspect the log file completely for status on all the components.
Time            : Wed Mar 26 12:23:51 2008
==============================================================
When I try to start SQL Server it times out. SQL Server Express is running ok.
Can you help me get this started?
Thank you,
Lucy

This is the previous errorlog:
2008-04-09 11:47:06.27 Server      Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
Mar 23 2007 16:28:52
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Evaluation Edition on Windows NT 6.0 (Build 6000: )
2008-04-09 11:47:06.27 Server      (c) 2005 Microsoft Corporation.
2008-04-09 11:47:06.27 Server      All rights reserved.
2008-04-09 11:47:06.27 Server      Server process ID is 240.
2008-04-09 11:47:06.27 Server      Authentication mode is WINDOWS-ONLY.
2008-04-09 11:47:06.27 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2008-04-09 11:47:06.27 Server      This instance of SQL Server last reported using a process ID of 4180 at 4/5/2008 11:17:36 AM (local) 4/5/2008 6:17:36 PM (UTC). This is an informational message only; no user action is required.
2008-04-09 11:47:06.27 Server      Registry startup parameters:
2008-04-09 11:47:06.27 Server      -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2008-04-09 11:47:06.27 Server      -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2008-04-09 11:47:06.27 Server      -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2008-04-09 11:47:06.32 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2008-04-09 11:47:06.32 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2008-04-09 11:47:06.50 Server      Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2008-04-09 11:47:06.55 Server      Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2008-04-09 11:47:06.64 Server      The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service.
2008-04-09 11:47:06.64 Server      Database mirroring has been enabled on this instance of SQL Server.
2008-04-09 11:47:06.64 spid4s      Starting up database 'master'.
2008-04-09 11:47:06.80 spid4s      4 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:06.82 spid4s      0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:06.82 spid4s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:07.06 spid4s      SQL Trace ID 1 was started by login "sa".
2008-04-09 11:47:07.10 spid4s      Starting up database 'mssqlsystemresource'.
2008-04-09 11:47:07.13 spid4s      The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2008-04-09 11:47:07.34 spid4s      Server name is 'USER-PC'. This is an informational message only. No user action is required.
2008-04-09 11:47:07.34 spid9s      Starting up database 'model'.
2008-04-09 11:47:07.53 spid9s      Clearing tempdb database.
2008-04-09 11:47:08.11 Server      A self-generated certificate was successfully loaded for encryption.
2008-04-09 11:47:08.11 Server      Server is listening on [ 'any' <ipv6> 1433].
2008-04-09 11:47:08.11 Server      Server is listening on [ 'any' <ipv4> 1433].
2008-04-09 11:47:08.17 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2008-04-09 11:47:08.17 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2008-04-09 11:47:08.17 Server      Server is listening on [ ::1 <ipv6> 1434].
2008-04-09 11:47:09.12 spid9s      Starting up database 'tempdb'.
2008-04-09 11:47:09.47 spid12s     The Service Broker protocol transport is disabled or not configured.
2008-04-09 11:47:09.47 spid12s     The Database Mirroring protocol transport is disabled or not configured.
2008-04-09 11:47:09.53 spid12s     Service Broker manager has started.
2008-04-09 11:51:06.92 Server      CPU time stamp frequency has changed from 1662000 to 199683 ticks per millisecond. The new frequency will be used.
2008-04-09 11:55:07.29 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 11:55:07.29 Server      CPU time stamp frequency has changed from 199683 to 136029 ticks per millisecond. The new frequency will be used.
2008-04-09 12:23:09.84 Server      CPU time stamp frequency has changed from 136029 to 586928 ticks per millisecond. The new frequency will be used.
2008-04-09 12:59:13.12 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 13:07:13.85 Server      CPU time stamp frequency has changed from 586928 to 824822 ticks per millisecond. The new frequency will be used.
2008-04-09 13:47:17.50 Server      CPU time stamp frequency has changed from 824822 to 140502 ticks per millisecond. The new frequency will be used.
2008-04-09 14:07:19.33 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 15:07:24.80 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 15:11:25.16 Server      CPU time stamp frequency has changed from 140502 to 1413355 ticks per millisecond. The new frequency will be used.
2008-04-09 15:15:25.53 Server      CPU time stamp frequency has changed from 1413355 to 161989 ticks per millisecond. The new frequency will be used.
2008-04-09 15:19:25.89 Server      CPU time stamp frequency has changed from 161989 to 134822 ticks per millisecond. The new frequency will be used.
2008-04-09 16:23:31.73 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 17:23:37.20 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 18:11:41.58 Server      CPU time stamp frequency has changed from 134822 to 154257 ticks per millisecond. The new frequency will be used.
2008-04-09 18:23:42.67 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 18:23:42.67 Server      CPU time stamp frequency has changed from 154257 to 134721 ticks per millisecond. The new frequency will be used.
2008-04-09 18:35:43.79 Server      CPU time stamp frequency has changed from 134721 to 151448 ticks per millisecond. The new frequency will be used.
2008-04-09 18:43:44.51 Server      CPU time stamp frequency has changed from 151448 to 125134 ticks per millisecond. The new frequency will be used.
2008-04-09 19:15:47.35 Server      CPU time stamp frequency has changed from 125134 to 182297 ticks per millisecond. The new frequency will be used.
2008-04-09 19:23:48.08 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 19:27:48.45 Server      CPU time stamp frequency has changed from 182297 to 120770 ticks per millisecond. The new frequency will be used.
2008-04-09 19:47:50.27 Server      CPU time stamp frequency has changed from 120770 to 1370171 ticks per millisecond. The new frequency will be used.
2008-04-09 20:07:52.10 Server      CPU time stamp frequency has changed from 1370171 to 106932 ticks per millisecond. The new frequency will be used.
2008-04-09 20:23:53.56 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 20:35:54.65 Server      CPU time stamp frequency has changed from 106932 to 88924 ticks per millisecond. The new frequency will be used.
2008-04-09 20:51:56.11 Server      CPU time stamp frequency has changed from 88924 to 102106 ticks per millisecond. The new frequency will be used.
2008-04-09 20:59:56.84 Server      CPU time stamp frequency has changed from 102106 to 118592 ticks per millisecond. The new frequency will be used.

Connection refused in SQL Server 2005

I have just installed SQL Server 2005 Developer Edition, and
I still have SQL Server 7 running on port 1433.
I have many SQL7 databases connected to CF7.0.2
When I try to connect to a new database that I can read and
write to in SQL2005, I get a connection refused error.
I'm not sure what port to connect to as SQL2005 port shows 0
which apparently means dynamic port allocation.
When I try port 1434 I get connection refused.
I have user name set to sa (and this is enabled in SQL2005)
and no password (windows authentication). Same result if user name
is blank.
Anyone got any idea what these settings should be?
Doug

I have now switched off dynamic port allocation and changed
the port to 1435 and I think I now connect to SQL Server 2005, but
I now get the error:
The user is not associated with a trusted SQL Server
connection.
I have tried using sa and tried setting up another user name,
but cannot get past this error.
Any help would be appreciated.
Doug

Sql server 2005, R/3 4.6c and compability mode

Hi
I doing upgrade from 4.6c --> ECC 6.0 on sql server 2005. And i get followin error
SCRIPT MSSINCHK
=================
Msg 468, Level 16, State 9, Server MEDIASP10, Line 55
Cannot resolve the collation conflict between "SQL_Latin1_General_CP850_BIN" and
"SQL_Latin1_General_CP850_BIN2" in the equal to operation.
Msg 468, Level 16, State 9, Server MEDIASP10, Line 66
Cannot resolve the collation conflict between "SQL_Latin1_General_CP850_BIN" and
"SQL_Latin1_General_CP850_BIN2" in the equal to operation.
Execution completed successfully
I have checked that collation order is correct.
I think that problem that somehow sql server's compability mode is recognized wrong (sql server 2000 insted sql server 2005).
Any colution on this ?
Br, Juha Niemi

Hi there,
I'm running into this same issue when trying to run PREPARE for the 4.6c to ERP/ECC 6.0 upgrade in phase INITPUT_PRE. I ran several of the queries mentioned in this thread and discovered that the database and instance are both BIN2, and 116230 columns are BIN2, but another 319398 columns are still BIN. Without reverting the database (eek, somehow) back to MSSQL2000 and rerunning instcoll.exe (again, I already did once) or building an alter table query for each one that is out of spec (which according to MSDN won't work on certain cols anyway), how can this be resolved?
for my SID database I have the following column types in count:
SQL_Latin1_General_CP850_BIN2     116230
Latin1_General_BIN     29
NULL     58467
Latin1_General_CI_AS_KS_WS     11
SQL_Latin1_General_CP850_BIN     319398
But the databases are all running BIN2 as such:
Server     SQL_Latin1_General_CP850_BIN2
Master     SQL_Latin1_General_CP850_BIN2
Model     SQL_Latin1_General_CP850_BIN2
TempDB     SQL_Latin1_General_CP850_BIN2
SID     SQL_Latin1_General_CP850_BIN2
The checkdb procedure came back with no errors:
CHECKDB found 0 allocation errors and 0 consistency errors in database 'PD1'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
And the system appears to be functioning correctly, except that the Upgrade Assistant won't let me continue with the mismatched column collation types.
Suggestions? I noticed there was never a resolution posted.
Thanks,
--ben

Import data from postgreSQL into SQL server 2005

I am trying to import one table from postgreSQL to SQL Server 2005 using sql server import and export wizard. When i test the connection after providing data source, location, username, password in the Data Link Properties section I get the message "Test Connection Succeeded". As soon as i press next to go onto next step i get the following error.
TITLE: SQL Server Import and Export Wizard
Cannot get string literals from the database connection "Provider=PostgreSQL.1;User ID=sa;Data Source=localhost;Location=TestMasterMap;Extended Properties=".
ADDITIONAL INFORMATION:
Object reference not set to an instance of an object. (DTSWizard)
BUTTONS:
OK
I have tried all sorts of different combinations for these properties but it always fails on this step. Can anybody help me with this?

The settings above worked for a small table with 3 rows. Now when I try to import the bigger table which I wanted to import in the first instance I get following out of memory error. Anybody knows how to work around this. I have checked my task manager and more than half of my memory was still not used when I get this error.
TITLE: SQL Server Import and Export Wizard
Column information for the source and destination data could not be retrieved.
"Query" -> [temporary].[dbo].[exporttable]:
- ERROR [HY000] Out of memory while reading tuples.;
No query has been executed with that handle
ADDITIONAL INFORMATION:
ERROR [HY000] Out of memory while reading tuples.;
No query has been executed with that handle (PSQLODBC.DLL)
BUTTONS:
OK

MS SQL Server 2005 Service Pack 1

Hello,
Does anyone know if SAP Business One SP1 PL4 is compatible with the newly available SQL Server 2005 SP1?
thanks,
Grace

Hi All,
I am running SQL 2005 SP1 with SBO without any problems. I am not sure if it is supported. SP1 for SQL solves a major memory problem that they had before SP1.
Our local SAP guys says that SQL 2005 is only supported on SBO 2005 SP1.
Hope it helps,
Adele

Restoring a SQL Server 2005 DB to a SQL Server 2014 install, is there any way to prevent it from being upgraded

Does anyone know if there is a flag I can use to prevent a SQL Server 2005 database from being upgraded to SQL 2014 when it is restored to a 2014 instance?
Don't ask why, I just need to know if this is possible or if 2005/8 DB's are required to be upgraded if they are going to run on SQL 2012/2014 instances. The documentation seems to say this is so, I just want to verify that.

First: You cannot directly restore a 2005 database to
2014. MS supports migration over 3 SQL Server version steps; means you can restore 2005 to 2008/2008R2/2012, but not to 2014. You have to do a migration step between.
Olaf I was looking for this today, because I'm working with a new customer that have SQL 2005 and I have SQL 2014. And needed to restore a backup form the production server in my test server.
When I read what you write I think, oh no!! I have to install SQL 2012 in my server. But that it's not an option for me, and I say let me try to restore the DB first in 2014 and if not work install 2012.
You can restore a 2005 database to 2014 directly, and it works.
For reference the version number in the servers 2005 (9.0.4035 SP3) and 2014 (12.0.2000 RTM)
This is not related in any way to the original question that you answered (the file format will be upgraded to the new motor, that is sure).
I put this lines because in the future there will be some people searching about if possible to restore a 2005 DB to 2014, and like me will read your lines and think it's not possible and that can make a decision to buy 2012 and not 2014 to that new server they
will migrate.
Don't forget to mark the best replies as answers!

Can't see data in data tab - sql server 2005

hello,
i am connected to a sql server 2005 database (with jtds driver), the connection is ok, i see the tables but i can't see data in data tab.
i have an error : incorrect syntax
somebody can help me ?
thank's in advance
alex

definitely. I was going to say, make sure you have the privileges to read data.
From Microsoft SQL Server 2000 on, it is recommended that you are a member of the db_datareader - so that data in the database can be read
Barry

Unable to start SQL Server Browser service in Sql server 2005

we are unable to start the SQL browser service on one of our machine with below error.
I believe this to be the reason, why we could not connect to the instance with below error
I tried troubleshooting as mentioned here, by changing
value in registry from 1 to 0, but still no luck.
SQLservices are also running.
Please help on how to resolve this!

Hello,
You say that SQL Server Browser Service belongs to a SQL Server 2005, but based on the name of the instance is a SQL Server
2012 instance.
Do you have any issues installing/uninstalling SQL Server 2005 or 2012? One of them 32-bit and the other 64-bit?
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Unable to Access SQL Server 2005 Remotedly

Not sure if this is the right forum to post this...
After going through lot of old posts in various forums and changing lot of settings, i'm still not able to access my Server remotely.
This is Windows 2003 Server machine with Sonicwall Firewall, i have allowed Port 1433 in both Firewall and ISA and call is getting through but i'm getting following error msg :-
{"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"}
This machine is also having Sql Server 2000, and the SQL Server 2005 is installed with named instance.
My connection string is :-
"Data Source=192.168.0.1\MYSERVER;Initial Catalog=MyDatabase;Integrated Security=True"
In example above, i'm showing dummy values but actual string is having the actual live IP address and correct named instance and database.
If i use a local address like 192.168.0.1 then i'm able to connect.
My TCP/IP Address in Sql configuration is having my Live IP Address and the port 1433.
Any help will be highly appreciable..

i'm still checking on this. i have changed the port now to 1434 and changed in all places.
my connection string is also changed now, so now i'm using :- MYIP\MYSERVER,1434
now i'm getting a different error msg
{"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)"}
this can also be due to firewall or something else is blocking it, i will rechk n post back final answer.

Unable to connect SQL server 2005 databse with JSF applications !

Hello guys!
Help me out to connect SQL server 2005 Databse with JSF applications using JDBC-ODBC bridge. I'm working with Netbeans 6.1 IDE.
I tried for the basic applications but instead got this error:
"unable to deploy jdbc drivers to the <project>domain/lib"
Please help me out with working sample codes that connects MS SQL server 2005 DB with JSF!!
Thank you guys!

1) don't use the bridge driver
2) don't do database access from JSF
3) learn how to use your application server
4) learn how to use your IDE

SQL Server 2005 AWE memory allocation

Similar Messages

Maybe you are looking for