Stack dump: SQL Server keeps crushing

My SQL Server keeps crushing with a stack dump error saying:
(in the management studio error log):
spid197 External dump process return code 0x20000001. External Dump process returned no errors.
spid197 Stack signature for dump is 0x000000014A5D4200
How can I investigate this further and what do these errors mean... also what does this return code mean and what does this signature dump code mean and where can I read more about them?
Thanks in advance,
Dror

Support article on this and related errors:
FIX: SQL Server 2012, SQL Server 2008 R2 or SQL Server 2008 stops responding and a "Non-yielding Scheduler" error is logged
http://support.microsoft.com/kb/2699013
Another support article:
FIX: SQL Server 2005 or SQL Server 2008 may stop responding when you are performing a backup
http://support.microsoft.com/kb/960543
Also run DBCC CHECKDB to check for database corruption:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ea0099e9-3ad2-4713-8e4e-ca429041bf2d/sql-server-2008-r2-sp1-creates-dump-files-twice-a-minute-please-help?forum=sqldatabaseengine
Kalman Toth Database & OLAP Architect
SELECT Video Tutorials 4 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Similar Messages

SQL Server keeps assigning dbo Schema, even though I specify a different schema

I'm using T-SQL to Create a table.
No matter what I do, the table gets created as dbo.TableName.
When I use this script
USE CBirtDev
go
CREATE TABLE [Inventory.PurchaseOrigin]
   PurchaseOriginID       tinyint       NOT NULL   IDENTITY ( 1,1 ),
   PurchaseOrigin           varchar(30)   NOT NULL
   CONSTRAINT [PKPurchaseOrigin_PurchaseOriginID] PRIMARY KEY CLUSTERED ([PurchaseOriginID] ASC),
   CONSTRAINT [AKPurchaseOrigin_PurchaseOrigin] UNIQUE ([PurchaseOrigin] ASC)
go
It creates a table with the following name: dbo.Inventory.PurchaseOrigin, instead of Inventory.PurchaseOrigin.
Why is it ignoring my Inventory Schema? If I incorporate the Database name into the script like
CREATE TABLE CBirtDev.Inventory.PurchaseOrigin it gives me dbo.CBirtDev.Inventory.PurchaseOrigin.
Totally frustrated...please help.

problem is your []
it should be this
CREATE TABLE [Inventory].[PurchaseOrigin]
Wrapping everything inside [] will consider it as name of table and hence it creates table with name as
Inventory.PurchaseOrigin under your default schema ie dbo
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

How to get Database creation history in sql server

I have delete one database on my server, I want to know what was the MDF path for that Deleted database do we have any way to get that .?
Regards Vikas Pathak

Hello,
Once you delete the database SQL Server keeps information temporarily on the default trace about who deleted a database,
the name of the database (or object), at what time and the transaction number among the information provided. However, the default trace does not provide information about the location of the database files deleted.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Stack dump while trying to view the JNDI Tree on a managed server.

Hi,
We are running WLI 9.2.3.
I have a problem when trying to view the managed servers JNDI Tree via the Admin console. The admin servers JNDI tree appears to be fine, but trying to view the 1st managed servers JNDI Tree via the admin console keeps producing a stack dump.
Does anyone know why this would be? Is it a security issue, judging by the classes below:
####<Jul 14, 2010 1:31:29 PM BST> <Warning> <RMI> <sofatd2b> <tgri02_rsk_ms11> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel
<> <> <1279110689890> <BEA-080004> <An error was thrown by rmi server: weblogic.jndi.internal.RootNamingNode.listBindings(Ljava.lang.String;Ljava.util.Hashtable;)java.lang.StackOverflowError.
java.lang.StackOverflowError
at $Proxy5.isAccessAllowed(Unknown Source)
at com.bea.common.security.internal.service.AccessDecisionServiceImpl.isAccessAllowed(AccessDecisionServiceImpl.java:105)
at sun.reflect.GeneratedMethodAccessor202.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:61)
at $Proxy11.isAccessAllowed(Unknown Source)
at com.bea.common.security.internal.service.AuthorizationServiceImpl.isAccessAllowed(AuthorizationServiceImpl.java:81)
at sun.reflect.GeneratedMethodAccessor201.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.bea.common.security.internal.utils.Delegator$ProxyInvocationHandler.invoke(Delegator.java:61)
at $Proxy13.isAccessAllowed(Unknown Source)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:461)
at weblogic.security.service.AuthorizationManager.isAccessAllowed(AuthorizationManager.java:524)
at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:414)
at weblogic.jndi.internal.ServerNamingNode.checkLookup(ServerNamingNode.java:394)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:169)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:196)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:95)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:348)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:269)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
at javax.naming.InitialContext.lookup(InitialContext.java:351)

Hi,
if it works in Chrome then this Problem is related to IE.
Maybe the URL is to long? IE can "only" handle 2048 Characters.
Regards
-Seb.

Stack dump in 2005 server

Hi All,
Please help me in resolving this issue.
====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 9.00.5057.00
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
Computer type is AT/AT COMPATIBLE.
Bios Version is INTEL - 6040000
PhoenixBIOS 4.0 Release 6.0
Current time is 06:04:58 09/21/14.
2 Intel x86 level 6, 2600 Mhz processor (s).
Windows NT 5.2 Build 3790 CSD Service Pack 2.
Memory
MemoryLoad = 95%
Total Physical = 4095 MB
Available Physical = 165 MB
Total Page File = 9029 MB
Available Page File = 4848 MB
Total Virtual = 2047 MB
Available Virtual = 256 MB
**Dump thread - spid = 0, PSS = 0x00000000, EC = 0x00000000
***Stack Dump being sent to D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0010.txt
* BEGIN STACK DUMP:
* 09/21/14 06:04:58 spid 0
* Non-yielding Resource Monitor
* Short Stack Dump
select @@ version:
Microsoft SQL Server 2005 - 9.00.5057.00 (Intel X86) Mar 25 2011 13:50:04 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
Thanks in advance.

Hello,
These types of errors are related to memory pressure or working set trimming on the SQL Server instance. Please try to set the max server
memory option and leave 2 or 4 GB of RAM to the operating system.
sp_configure
'show advanced options', 1;
GO
RECONFIGURE;
GO
sp_configure
'max server memory', 4096;
GO
RECONFIGURE;
GO
The above code limits SQL Server Memory Manager to 4 GB.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Msg 8631 Internal error: Server stack limit has been reached on SQL Server 2012 from T-SQL script that runs on SQL Server 2008 R2

I have an Script mostly that is generated by SSMS which works with-out issue on SQL Server 2008, but when I attempt to run it on a new fresh install of SQL Server 2012 I get an Msg 8631. Internal error: Server stack limit has been reached. Please look for
potentially deep nesting in your query, and try to simplify it.
The script itself doesn't seem to be all that deep or nested. The script is large 2600 lines and when I remove the bulk of the 2600 lines, it does run on SQL Server 2012. I'm just really baffled why something that SQL Server generated with very
few additions/changes AND that WORKS without issue in SQL Server 2008 R2 would suddenly be invalid in SQL Server 2012
I need to know why my script which is working great on our current SQL Server 2008 R2 servers suddenly fails and won't run on an new SQL Server 2012 server. This script is used to create 'bulk' Replications on a large number of DBs saving a tremendous
amount of our time doing it the manual way.
Below is an 'condensed' version of the script which fails. I have removed around 2550 lines of specific sp_addarticle statements which are mostly just copy and pasted from what SQL Management Studio 'scripted' for me went I when through the Replication
Wizard and told it to save to script.
declare @dbname varchar(MAX), @SQL nvarchar(MAX)
declare c_dblist cursor for
select name from sys.databases WHERE name like 'dbone[_]%' order by name;
open c_dblist
fetch next from c_dblist into @dbname
while @@fetch_status = 0
begin
print @dbname
SET @SQL = 'DECLARE @dbname NVARCHAR(MAX); SET @dbname = ''' + @dbname + ''';
use ['+@dbname+']
exec sp_replicationdboption @dbname = N'''+@dbname+''', @optname = N''publish'', @value = N''true''
use ['+@dbname+']
exec ['+@dbname+'].sys.sp_addlogreader_agent @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1, @job_name = null
-- Adding the transactional publication
use ['+@dbname+']
exec sp_addpublication @publication = N'''+@dbname+' Replication'', @description = N''Transactional publication of database
'''''+@dbname+''''' from Publisher ''''MSSQLSRV\INSTANCE''''.'', @sync_method = N''concurrent'', @retention = 0, @allow_push = N''true'', @allow_pull = N''true'', @allow_anonymous = N''false'', @enabled_for_internet
= N''false'', @snapshot_in_defaultfolder = N''true'', @compress_snapshot = N''false'', @ftp_port = 21, @allow_subscription_copy = N''false'', @add_to_active_directory = N''false'', @repl_freq = N''continuous'', @status = N''active'', @independent_agent = N''true'',
@immediate_sync = N''true'', @allow_sync_tran = N''false'', @allow_queued_tran = N''false'', @allow_dts = N''false'', @replicate_ddl = 1, @allow_initialize_from_backup = N''true'', @enabled_for_p2p = N''false'', @enabled_for_het_sub = N''false''
exec sp_addpublication_snapshot @publication = N'''+@dbname+' Replication'', @frequency_type = 1, @frequency_interval = 1, @frequency_relative_interval = 1, @frequency_recurrence_factor = 0, @frequency_subday = 8,
@frequency_subday_interval = 1, @active_start_time_of_day = 0, @active_end_time_of_day = 235959, @active_start_date = 0, @active_end_date = 0, @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1
-- There are around 2400 lines roughly the same as this only difference is the tablename repeated below this one
use ['+@dbname+']
exec sp_addarticle @publication = N'''+@dbname+' Replication'', @article = N''TABLE_ONE'', @source_owner = N''dbo'', @source_object = N''TABLE_ONE'', @type = N''logbased'', @description = null, @creation_script =
null, @pre_creation_cmd = N''drop'', @schema_option = 0x000000000803509F, @identityrangemanagementoption = N''manual'', @destination_table = N''TABLE_ONE'', @destination_owner = N''dbo'', @vertical_partition = N''false'', @ins_cmd = N''CALL sp_MSins_dboTABLE_ONE'',
@del_cmd = N''CALL sp_MSdel_dboTABLE_ONE'', @upd_cmd = N''SCALL sp_MSupd_dboTABLE_ONE''
EXEC sp_executesql @SQL
SET @dbname = REPLACE(@dbname, 'dbone_', 'dbtwo_');
print @dbname
SET @SQL = 'DECLARE @dbname NVARCHAR(MAX); SET @dbname = ''' + @dbname + ''';
use ['+@dbname+']
exec sp_replicationdboption @dbname = N'''+@dbname+''', @optname = N''publish'', @value = N''true''
use ['+@dbname+']
exec ['+@dbname+'].sys.sp_addlogreader_agent @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1, @job_name = null
-- Adding the transactional publication
use ['+@dbname+']
exec sp_addpublication @publication = N'''+@dbname+' Replication'', @description = N''Transactional publication of database
'''''+@dbname+''''' from Publisher ''''MSSQLSRV\INSTANCE''''.'', @sync_method = N''concurrent'', @retention = 0, @allow_push = N''true'', @allow_pull = N''true'', @allow_anonymous = N''false'', @enabled_for_internet
= N''false'', @snapshot_in_defaultfolder = N''true'', @compress_snapshot = N''false'', @ftp_port = 21, @allow_subscription_copy = N''false'', @add_to_active_directory = N''false'', @repl_freq = N''continuous'', @status = N''active'', @independent_agent = N''true'',
@immediate_sync = N''true'', @allow_sync_tran = N''false'', @allow_queued_tran = N''false'', @allow_dts = N''false'', @replicate_ddl = 1, @allow_initialize_from_backup = N''true'', @enabled_for_p2p = N''false'', @enabled_for_het_sub = N''false''
exec sp_addpublication_snapshot @publication = N'''+@dbname+' Replication'', @frequency_type = 1, @frequency_interval = 1, @frequency_relative_interval = 1, @frequency_recurrence_factor = 0, @frequency_subday = 8,
@frequency_subday_interval = 1, @active_start_time_of_day = 0, @active_end_time_of_day = 235959, @active_start_date = 0, @active_end_date = 0, @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1
-- There are around 140 lines roughly the same as this only difference is the tablename repeated below this one
use ['+@dbname+']
exec sp_addarticle @publication = N'''+@dbname+' Replication'', @article = N''DB_TWO_TABLE_ONE'', @source_owner = N''dbo'', @source_object = N''DB_TWO_TABLE_ONE'', @type = N''logbased'', @description = null, @creation_script
= null, @pre_creation_cmd = N''drop'', @schema_option = 0x000000000803509D, @identityrangemanagementoption = N''manual'', @destination_table = N''DB_TWO_TABLE_ONE'', @destination_owner = N''dbo'', @vertical_partition = N''false''
EXEC sp_executesql @SQL
fetch next from c_dblist into @dbname
end
close c_dblist
deallocate c_dblist
George P Botuwell, Programmer

Hi George,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
If you have any feedback on our support, please click
here.
Allen Li
TechNet Community Support

Stack Dump while creating Write Optimized DSO on BW 7.3, MS SQL - any SAP Notes?

While attempting to create a Write Optimized DSO on BW 7.3, MS SQL, we had a stack dump - ABAP Program CL_RSD_ODSO_VERS==============CP with short text " Access using NULL object reference is not possible. "
Has anyone seen any SAP Notes on this subject?

Hi John,
Was any field deleted from the DSO, if yes, probably the system is not able to relate the pointer from the DSO table. Error like these come up very often when fields are deleted from DSO. Solution is to remove the field manually from the table also. However, the system is supposed to do but sometimes such ambiguity causes such issues.

Is there any way to activate the keep identity setting when using a Transfer SQL Server Object Task?

Is there any way to add the "Keep Identity" option to the tables selected for transfer in a Transfer SQL Server Object Task? It seems that would be very useful, yet I can't find an easily available setting for it. I would prefer to
accomplish this within the Transfer SQL Server Object Task since it can copy any new fields added to the source tables, as opposed to having to rebuild a custom Data Flow Task any time a table structure is altered. I thought setting "CopyPrimaryKeys"
to True would do the trick, but I found that only ensures that the column settings are transferred; when the transfer happens, the destination id column is populated based on the specified seed and increment value, not what's actually in the source table.
I'd like to point out that replication isn't really an option here. This is a package that runs a few times a day to keep some data on our website up to date with data in our protected corporate environment.

IIRW there is FastLoadKeepIdentity specifies
whether to keep an identity in OLEDB destination
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Can a SQL Server dump be loaded into oracle?

Hi All,
I'm wondering, if we have a sql server DB dump, is there anyway to load the data into Oracle? (other than loading the dump into a sql server and then using OMWB? )
Thanks in advance,
Sudheer

Yes, you can migrate just the table structure if you want. After you have sucessfully created an Oracle Model using the capture wizard. You can invoke the "Generate Migration Scripts..." from the Action menu.
This will create a SQL script, which you can modify as necessary and then execute from SQL*Plus or SQL Developer.
Donal

Is it possible to load a dump file collected from sql server to orcle 10gR2

Hi..
As a part of data migration from legacy systems , we need to migrate only required tables from Sql server to Oracle 10gr2 .
At present client is telling that he will give it as dump file.
My question is , Is it possible to load the dump file collected from sql server to oracle 10gR2?
Thanks in advance ..

yes, it is.
Using for example SQL Developer Migration Workbench even allows you to create unload scripts for the desired SQL Server tables and it also creates the DDL scripts for you to create the Oracle tables similar to the SQL Server table AND it alows creates the SQL*Loader scripts that allow you to load the SQL Server generated dump file into the Oracle db.
Here the link:
http://www.oracle.com/technology/tech/migration/workbench/index_sqldev_omwb.html
If you do not want to use this utility, you can also use SQL*Loader to load the content of the SQL Server dump file into the Oracle database; but in this case you have to write the whole SQL*Loader control scripts on your own.
Edited by: kgronau on Sep 16, 2009 1:54 PM

Data Import from Oracle Dump to SQL Server(2000/2005)

Hi Friends,
I'm using Oracle 10g.
I've a scenario.
I've Oracle Dump file. Now i would like import in SQL Server(2000/2005).
Can any one suggest me how to do this?
Any idea,clue will be highly appreciated.

I think you will need to import the data into SQL Server from an ASCII flat file using SQL Server DTS if avialable. You can use SQL Plus to extract the data outof Oracle into comma delimited flat files and then use SQL Server DTS load into the SQL Server database.

Importing English Wikipedia dump (large .xml file) into SQL server 2012

Hi there,
I've downloaded the latest English Wikipedia dump (enwiki-latest-pages-articles.xml),
and I'm trying to import it to SQL server 2012 by using XML Bulk Load. This is the VBScript
code I've used:
Dim objBL
Set objBL = CreateObject("SQLXMLBulkLoad.SQLXMLBulkload.4.0")
objBL.ConnectionString = "provider=SQLOLEDB;data source=localhost;database=tempdb;integrated security=SSPI"
objBL.ErrorLogFile = "error.log"
objBL.CheckConstraints=true
objBL.XMLFragment = True
objBL.SchemaGen = True
objBL.SGDropTables = True
objBL.Execute "export-0.8.xml", "enwiki-latest-pages-articles.xml"
Set objBL = Nothing
This VBScript should generate the tables and load the Wikipedia XML file into them. The VBScript code also uses the wikimedia
XSD schema. However, I'm getting this error:
Any help with this problem would be appropriate!

Why not try looking at this:
http://technet.microsoft.com/en-us/library/ms191184.aspx
If this is helpful please mark it so. Also if this solved your problem mark as answer.

SQL Server 2012 Express LocalDB parm for keeping unicode char

in developer's windows 8.1 pc, the SQL Server 2012 Express LocalDB does not seem to keep Unicode like \U2221. it get translated to the plain - instead of keeping as
−.
what parameter od I need to setup to make sure it keep such character as is

Hi fs - ab,
You know that this forum is to discuss the VS IDE, to make this issue clearly, could you share us a screen shot for this issue? Where did you change your localDB with Unicode?
I did some research about it.
LocalDB supports two kinds of instances: Automatic instances and named instances.
•Automatic instances of LocalDB are public. They are created and managed automatically for the user and can be used by any application. One automatic instance of LocalDB exists for every version of LocalDB installed
on the user’s computer. Automatic instances of LocalDB provide seamless instance management. There is no need to create the instance; it just works. This allows for easy application installation and migration to a different computer. If the target machine
has the specified version of LocalDB installed, the automatic instance of LocalDB for that version is available on the target machine as well. Automatic instances of LocalDB have a special pattern for the instance name that belongs to a reserved namespace.
This prevents name conflicts with named instances of LocalDB. The name for the automatic instance is a single v character followed by the LocalDB release version number in the format xx.x. For example, v11.0 represents SQL Server 2012.
•Named instances of LocalDB are private. They are owned by a single application that is responsible for creating and managing the instance. Named instances provide isolation from other instances and can improve performance
by reducing resource contention with other database users. Named instances must be created explicitly by the user through the LocalDB management API or implicitly via the app.config file for a managed application (although managed application may also use
the API, if desired). Each named instance of LocalDB has an associated LocalDB version that points to the respective set of LocalDB binaries. The instance name of a LocalDB is sysname data type and can have up to 128 characters. (This differs from regular
named instances of SQL Server, which limits names to regular NetBIOS names of 16 ASCII chars.) The name of an instance of LocalDB can contain any Unicode characters that are legal within a filename.
A named instance that uses an automatic instance name becomes an automatic instance.
Reference:
http://technet.microsoft.com/en-us/library/hh510202(v=sql.110).aspx
It seems that it is related to the SQL Server, am I right? If so, maybe the SQL Server forum would be better for this issue.
If I have misunderstood this issue, please feel free to let me know.
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

SQL Server 2012 Express LocalDB parm for keeping unicode char from TextBox

Platform: developer's windows 8.1 pc with visual studio 2012 pro, .net 4.5, sql express 2012 express and localDB
in a textbox, say textTbx on a windows form, if there is Unicode like \U2221, I can have to save to file and read back without change using textTbx.Text value.
however for the content in the textTbx.Text value, upon saving to
SQL Server 2012 Express LocalDB, and then retrieved, the content gets changed for some Unicode like
U2221. it get translated to the plain - instead of keeping as
−.
what parameter do I need to setup to make sure it keep such character as is?
Btw: I had posted to visual studio general forum but was asked to post here

Platform: developer's windows 8.1 pc with visual studio 2012 pro, .net 4.5, sql express 2012 express and localDB
in a textbox, say textTbx on a windows form, if there is Unicode like \U2221, I can have to save to file and read back without change using textTbx.Text value.
however for the content in the textTbx.Text value, upon saving to
SQL Server 2012 Express LocalDB, and then retrieved, the content gets changed for some Unicode like
U2221. it get translated to the plain - instead of keeping as
−.
what parameter do I need to setup to make sure it keep such character as is?
Btw: I had posted to visual studio general forum but was asked to post here
Hello,
In this case, we could convert the text value to varbinary type before storing them to sql, and we could convert it back to the encoded one, you could change UTF-8 to the one you are dealing with.
You could refer to the suggestions shared by Filip Ekberg in the following thread.
http://stackoverflow.com/questions/11859926/load-or-convert-varbinary-from-sql-to-textbox-text
Here's an example on how you convert a text to bytes and then back again:
var bytes = Encoding.UTF8.GetBytes("test");
This will give you a byte array that looks like this:
{ 116, 101, 115, 116 }
Now to get the text again, you can use Encoding.UTF8.GetString() like this:
Encoding.UTF8.GetString(bytes);
This means that you could simple do this when saving the value:
cmdb.Parameters.AddWithValue("@text", Encoding.UTF8.GetBytes(textreview.Text));
And then when loading it back you simply do this:
textreview.Text = Encoding.GetString((byte[])dr["text"]);
Regards.
Carl
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

All System Centre Stack on 1 Instance of SQL Server

Apologies : there does not appear to be a forum where this fits
I am in the process of doing a design for a client who wants the whole system centre stack installed but on one instance of a SQL 2012 Cluster.
I can find
SQL Server Requirements for System Center 2012 R2:
https://technet.microsoft.com/en-us/library/dn281933.aspx
which states "
For testing purposes only, one SQL Database Engine Services instance may be used for all components, but is not recommended in a production setting due to performance concerns."
however what I need is something to back this up and there does not appear to be anything available.
Can someone please point me in the right direction for something to back this up.
regards
Andy

Not only is it a truly bad idea but it is not possible.
You will find a lot of information on the subject here
http://www.systemcentercentral.com/sql-instances-and-system-center-2012-sysctr-sql-scom-sccm-scsm/
Example:
Components of System Center 2012 which uses SRS cannot share the reporting services instance. Components with SRS based reporting include: Operations Manager, Service Manager, Configuration Manager, Data Protection Manager.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Stack dump: SQL Server keeps crushing

Similar Messages

Maybe you are looking for