<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" version="2.0"><channel><atom:id>tag:blogger.com,1999:blog-6510244423305214811</atom:id><lastBuildDate>Fri, 06 Sep 2024 02:23:39 +0000</lastBuildDate><category>ase</category><category>sybase</category><category>systemtables</category><category>tips</category><category>recovery</category><category>storage</category><category>tempdb</category><category>query</category><category>sql</category><category>DBA Sidekick</category><category>android</category><category>backup</category><category>book</category><category>dbcc</category><category>error message 946</category><category>error message guide</category><category>free</category><category>linux</category><category>login</category><category>mobile</category><category>replication</category><category>sa</category><category>space</category><category>spid</category><category>stored procedure</category><category>tables</category><category>tools</category><category>ubuntu</category><category>virtual</category><category>virtualbox</category><title>Sybase Tips,Solutions,Administration</title><description></description><link>http://sybaseadmin.blogspot.com/</link><managingEditor>noreply@blogger.com (Sri)</managingEditor><generator>Blogger</generator><openSearch:totalResults>28</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-1681118318603226285</guid><pubDate>Thu, 19 Jan 2012 11:18:00 +0000</pubDate><atom:updated>2012-01-19T16:48:32.965+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">android</category><category domain="http://www.blogger.com/atom/ns#">ase</category><category domain="http://www.blogger.com/atom/ns#">DBA Sidekick</category><category domain="http://www.blogger.com/atom/ns#">error message guide</category><category domain="http://www.blogger.com/atom/ns#">mobile</category><title>ASE Error messages on Android mobile</title><description>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
Yes,today i found this interesting application &lt;b&gt;DBA Sidekick(sybase) &lt;/b&gt;on android market.But not tried.I think it is useful to DBAs.&lt;br /&gt;
If any one used this application ,post a comment on this.&lt;br /&gt;
&lt;br /&gt;
Here is the link for the android application&lt;br /&gt;
&lt;br /&gt;
&lt;a href=&quot;https://market.android.com/details?id=com.businesscompassllc.dbasidekicksybase&amp;amp;hl=en&quot;&gt;https://market.android.com/details?id=com.businesscompassllc.dbasidekicksybase&amp;amp;hl=en&lt;/a&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;/div&gt;</description><link>http://sybaseadmin.blogspot.com/2012/01/ase-error-messages-on-android-mobile.html</link><author>noreply@blogger.com (Sri)</author><thr:total>4</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-1726888625020091999</guid><pubDate>Wed, 11 Jan 2012 05:08:00 +0000</pubDate><atom:updated>2012-01-11T10:38:48.911+05:30</atom:updated><title>List all stored procedures in ASE</title><description>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
 &lt;span&gt;&lt;span class=&quot;google-src-text&quot; style=&quot;direction: ltr; text-align: left;&quot;&gt;use sybsystemprocs&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;
&lt;span&gt;&lt;span class=&quot;google-src-text&quot; style=&quot;direction: ltr; text-align: left;&quot;&gt;select name from sysobjects where type=&#39;P&#39;&lt;/span&gt;&amp;nbsp;&lt;/span&gt;&lt;/div&gt;</description><link>http://sybaseadmin.blogspot.com/2012/01/list-all-stored-procedures-in-ase.html</link><author>noreply@blogger.com (Sri)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-3897778457976686813</guid><pubDate>Wed, 11 Jan 2012 05:04:00 +0000</pubDate><atom:updated>2012-01-11T10:35:10.978+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><category domain="http://www.blogger.com/atom/ns#">error message 946</category><category domain="http://www.blogger.com/atom/ns#">stored procedure</category><category domain="http://www.blogger.com/atom/ns#">sybase</category><category domain="http://www.blogger.com/atom/ns#">systemtables</category><title>sp_dbremap</title><description>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
A special procedure to be run only when instructed by ASE error message 
number 946. The procedure synchronizes the definition of a database in 
sysusages and memory.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;sp_dbremap&lt;/b&gt; &lt;dbname&gt;&lt;/dbname&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;ul&gt;
&lt;li class=&quot;fi&quot;&gt;If an &lt;b&gt;alter database&lt;/b&gt;&amp;nbsp; statement issued on a database that is in the process
of being dumped is interrupted, Adaptive Server prints a message
instructing the user to execute &lt;b&gt;sp_dbremap&lt;/b&gt;.&lt;br /&gt;


&lt;/li&gt;
&lt;li class=&quot;ds&quot;&gt;Any
changes to &lt;b&gt;&lt;i&gt;sysusages&lt;/i&gt;&lt;/b&gt; during a database or transaction
dump are not copied into active memory until the dump completes,
to ensure that database mapping does not change during the dump.
Running alter database&amp;nbsp; while doing database dump&amp;nbsp; makes
changes to system tables on the disk immediately. In-memory
allocations cannot be changed until a dump completes. so alter database operation pauses.&lt;br /&gt;


When you execute &lt;b&gt;sp_dbremap&lt;/b&gt;, it
must wait until the dump process completes.&lt;br /&gt;


&lt;/li&gt;
&lt;li class=&quot;ds&quot;&gt;If you are instructed to run &lt;b&gt;sp_dbremap&lt;/b&gt;,
but do not do it, the space you have allocated with alter database does not become available to Adaptive Server until
the next restart.&lt;br /&gt;


&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><link>http://sybaseadmin.blogspot.com/2012/01/spdbremap.html</link><author>noreply@blogger.com (Sri)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-2575995334015034801</guid><pubDate>Mon, 09 Jan 2012 15:26:00 +0000</pubDate><atom:updated>2012-01-09T21:07:00.262+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><category domain="http://www.blogger.com/atom/ns#">recovery</category><category domain="http://www.blogger.com/atom/ns#">sybase</category><category domain="http://www.blogger.com/atom/ns#">tempdb</category><title>Troubleshoot if  tempdb gets filled</title><description>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;br /&gt;
&amp;nbsp;Try to find out the Active process that is filling up the temp db space.&lt;br /&gt;
&lt;br /&gt;
1)&amp;nbsp; If the transaction log of tempdb is full then you can login through sa and type following command.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;1&amp;gt; dump tran tempdb with truncate_only&lt;br /&gt;2&amp;gt; go&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
2) If the database is full then you can increase the size of the database on a free device.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;1&amp;gt; alter database tempdb on device_name = size&lt;br /&gt;2&amp;gt; go&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
3) use following command It will abort all open transactions.&lt;br /&gt;
&lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp; But be sure the task by confirming with the concern users.&lt;br /&gt;
&lt;br /&gt;
&lt;b&gt;1&amp;gt;select lct_admin(0,2)&lt;br /&gt;2&amp;gt;go&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
Restarting the server is not recommanded.&lt;br /&gt;
lct_admin (0,2) would abort all open transactions, or you can go for altering the tempdb space. &lt;b&gt;Multiple tempdb&#39;s&lt;/b&gt; is a feature which can be implemented to minimize such issues of tempdb getting full.&lt;br /&gt;
&lt;br /&gt;
Previously posted article on same topic refer that also.&lt;br /&gt;
http://sybaseadmin.blogspot.com/2011/12/temp-db-full.html&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;nbsp; &lt;br /&gt;
&lt;span style=&quot;font-size: x-small;&quot;&gt;&lt;span style=&quot;font-family: &amp;quot;Trebuchet MS&amp;quot;,sans-serif;&quot;&gt;&lt;/span&gt;&lt;/span&gt;&lt;/div&gt;</description><link>http://sybaseadmin.blogspot.com/2012/01/troubleshoot-if-your-tempdb-gets-filled.html</link><author>noreply@blogger.com (Sri)</author><thr:total>23</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-3175918871910826327</guid><pubDate>Wed, 28 Dec 2011 11:08:00 +0000</pubDate><atom:updated>2012-01-03T22:16:19.791+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><category domain="http://www.blogger.com/atom/ns#">query</category><category domain="http://www.blogger.com/atom/ns#">systemtables</category><title>List Server Reserved Words</title><description>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;span class=&quot;Apple-style-span&quot; style=&quot;color: #333333; font-family: Verdana; font-size: 14px; line-height: 20px;&quot;&gt;Run this simple query in isql to find all the reserved words for Adaptive Server Enterprise .&lt;br /&gt;
&amp;nbsp;To list all reserved words for Adaptive Server Enterprise, log in to isql and run this query:&lt;br /&gt;
&lt;br /&gt;
&lt;ol class=&quot;code&quot; style=&quot;margin: 0px; padding: 0px 0px 0px 35px;&quot;&gt;&lt;code style=&quot;font: 1.1em &#39;Courier New&#39;,Courier,Fixed;&quot;&gt;&lt;b&gt;&amp;nbsp;&lt;/b&gt;select name from spt_values where type = &quot;W&quot;&lt;/code&gt;&lt;/ol&gt;
&lt;ol class=&quot;code&quot; style=&quot;margin: 0px; padding: 0px 0px 0px 35px;&quot;&gt;&lt;code style=&quot;font: 1.1em &#39;Courier New&#39;,Courier,Fixed;&quot;&gt;&lt;b&gt;&lt;br /&gt;&lt;/b&gt;&lt;/code&gt;&lt;/ol&gt;
&lt;ol class=&quot;code&quot; style=&quot;margin: 0px; padding: 0px 0px 0px 35px;&quot;&gt;&lt;code style=&quot;font: 1.1em &#39;Courier New&#39;,Courier,Fixed;&quot;&gt;&lt;b&gt;&lt;br /&gt;&lt;/b&gt;&lt;/code&gt;&lt;/ol&gt;
The spt_values table is a look-up table in the master database that stores system values used by other server processes.&lt;/span&gt;&lt;br /&gt;
&lt;br /&gt;&lt;/div&gt;</description><link>http://sybaseadmin.blogspot.com/2011/12/list-server-reserved-words.html</link><author>noreply@blogger.com (Sri)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-6513137790375853493</guid><pubDate>Mon, 26 Dec 2011 17:18:00 +0000</pubDate><atom:updated>2011-12-26T23:38:27.360+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><category domain="http://www.blogger.com/atom/ns#">linux</category><category domain="http://www.blogger.com/atom/ns#">sybase</category><category domain="http://www.blogger.com/atom/ns#">tips</category><category domain="http://www.blogger.com/atom/ns#">ubuntu</category><category domain="http://www.blogger.com/atom/ns#">virtual</category><category domain="http://www.blogger.com/atom/ns#">virtualbox</category><title>Installing sybase on ubuntu</title><description>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
Just&amp;nbsp; installed ASE15.0.3 ESD#1&amp;nbsp; on ubuntu 7.04 inside virtual box.&lt;br /&gt;
&lt;br /&gt;
Download the  ASE Developer’s Edition.&lt;br /&gt;
&lt;br /&gt;
1)Install the following package(Need to put&amp;nbsp; ubuntu 7.04 CD /DVD in Drive).&lt;br /&gt;
&lt;br /&gt;
&lt;pre&gt;apt-get install libaio1 &lt;/pre&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
2)Sybase requires at lea Ist 300 MB shared memory,so increase.&lt;br /&gt;
&lt;br /&gt;
&lt;pre&gt;/sbin/sysctl -w kernerl.shmmax=300000000&lt;/pre&gt;
&lt;br /&gt;
&lt;br /&gt;
3)Unzip sybase installation file&lt;br /&gt;
&lt;br /&gt;
&lt;pre&gt;tar -xvf ase_1503_linuxx86.tgz&lt;/pre&gt;
&lt;br /&gt;
&lt;br /&gt;
4)Now run the setup&lt;br /&gt;
&lt;br /&gt;
&lt;pre&gt;chmod +x ./setup&lt;/pre&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Choose Express Edition install while installing.&lt;br /&gt;
&lt;br /&gt;
5)Append&amp;nbsp; the contents of the SYBASE.sh to /etc/bash.bashrc.&lt;br /&gt;
&lt;br /&gt;
6)We need to add sybase shared libraries to the library path.&lt;br /&gt;
&lt;br /&gt;
&lt;pre&gt;gedit /etc/ld.so.conf.d/sybase.conf&lt;/pre&gt;
&lt;br /&gt;
&lt;br /&gt;
7)Add these lines to the above file&lt;br /&gt;
&lt;br /&gt;
&lt;pre&gt;/opt/sybase/OCS-15_0/lib3p
/opt/sybase/ASE-15_0/lib&lt;/pre&gt;
&lt;br /&gt;
&lt;br /&gt;
8)Afterwards, update the paths&lt;br /&gt;
&lt;br /&gt;
&lt;pre&gt;/sbin/ldconfig&lt;/pre&gt;
&lt;br /&gt;
&lt;br /&gt;
9)In
/opt/sybase/locales/locales.dat&lt;br /&gt;
&lt;br /&gt;
Find the section:&lt;br /&gt;
[linux]&lt;br /&gt;
&lt;br /&gt;
&amp;nbsp;Add the line:&lt;br /&gt;
&lt;pre&gt;locale = en_IN, us_english, iso_1&lt;/pre&gt;
&lt;/div&gt;</description><link>http://sybaseadmin.blogspot.com/2011/12/installing-sybase-on-ubuntu.html</link><author>noreply@blogger.com (Sri)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-1265406312678406162</guid><pubDate>Mon, 26 Dec 2011 04:41:00 +0000</pubDate><atom:updated>2011-12-26T10:12:18.310+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><category domain="http://www.blogger.com/atom/ns#">recovery</category><category domain="http://www.blogger.com/atom/ns#">sybase</category><category domain="http://www.blogger.com/atom/ns#">tempdb</category><title>Temp db full</title><description>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
Since ASE 12.5 we can create a user defined tempdb (using sp_tempdb)
 and bind an admin login&lt;br /&gt;
&amp;nbsp;to this new tempdb.&amp;nbsp;This admin account can then run sp_who to find out who filled tempdb and kill the process.&lt;br /&gt;
&lt;br /&gt;
Sometimes the kill won&#39;t work

The new &#39;multiple tempdb&#39; feature in 12.5.0.3 allows you to avoid the
problem that &lt;b&gt;tempdb is full and &amp;nbsp;cannot access the fake tables in
master&lt;/b&gt;.&lt;br /&gt;
In pre-12.5.0.3, we can get some information from different sources,
like dbcc pss, dbcc lock and dbcc log&lt;br /&gt;
&lt;br /&gt;
Follow these steps to solve tempdb full&lt;br /&gt;
&lt;br /&gt;
&amp;nbsp;(i) use &lt;b&gt;&#39;tempdb_space&#39;&lt;/b&gt; resource limits (in 12.5+) and&lt;br /&gt;
&lt;br /&gt;
&amp;nbsp;(ii) if your tempdb gets full anyway,use lct_admin to abort the transactions causing this.&lt;br /&gt;
&amp;nbsp;Instead of this &amp;nbsp;it&#39;s a good idea to&lt;br /&gt;
&lt;br /&gt;
&amp;nbsp;(iii) enable the &lt;b&gt;&#39;abort tran on log
full&#39;&lt;/b&gt; option for tempdb so that &lt;b&gt;LOG SUSPEND&lt;/b&gt; statuses will not remain
until the DBA takes action.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;/div&gt;</description><link>http://sybaseadmin.blogspot.com/2011/12/temp-db-full.html</link><author>noreply@blogger.com (Sri)</author><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-1675899825046503639</guid><pubDate>Sun, 25 Dec 2011 15:21:00 +0000</pubDate><atom:updated>2011-12-25T20:52:06.529+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><category domain="http://www.blogger.com/atom/ns#">dbcc</category><category domain="http://www.blogger.com/atom/ns#">spid</category><category domain="http://www.blogger.com/atom/ns#">sybase</category><category domain="http://www.blogger.com/atom/ns#">tempdb</category><title>orphan tables in tempdb</title><description>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
If an spid
that owns the table no longer exists in sysprocesses.&lt;br /&gt;
This happens
sometimes when a killed spid isn&#39;t cleaned up properly,&lt;br /&gt;
leaving
temp tables behind.&amp;nbsp; These are called &quot;orphaned&quot; temp tables.
&lt;br /&gt;
&lt;br /&gt;Running
&lt;br /&gt;
&lt;br /&gt;&lt;pre&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;dbcc orphantables&lt;/pre&gt;
&lt;br /&gt;
&lt;br /&gt;will list orphaned tables in tempdb .&lt;br /&gt;
&lt;br /&gt;&lt;pre&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;dbcc orphantables (&quot;drop&quot;)&lt;/pre&gt;
&lt;br /&gt;
&lt;br /&gt;will try to clean them up.&lt;/div&gt;</description><link>http://sybaseadmin.blogspot.com/2011/12/orphan-tables-in-tempdb.html</link><author>noreply@blogger.com (Sri)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-5932866662583876052</guid><pubDate>Fri, 23 Dec 2011 11:41:00 +0000</pubDate><atom:updated>2011-12-23T17:14:47.150+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><category domain="http://www.blogger.com/atom/ns#">query</category><category domain="http://www.blogger.com/atom/ns#">space</category><category domain="http://www.blogger.com/atom/ns#">sybase</category><category domain="http://www.blogger.com/atom/ns#">systemtables</category><category domain="http://www.blogger.com/atom/ns#">tables</category><title>Top 10 large tables in database</title><description>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
&lt;b&gt;Top 10 largest tables in a database by rowcount:
&lt;/b&gt;&lt;br /&gt;
&lt;pre&gt;select

top 10

&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;name,

&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;row_count(db_id(), id)

from

&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;sysobjects

order by

&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;row_count(db_id(),id) desc
&lt;/pre&gt;
&lt;br /&gt;
&lt;b&gt;Top 10 largest tables in a database by allocated space:
&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;pre&gt;select

top 10

&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;name,

&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;reserved_pages(db_id(),id)

/(1024.0 / (@@maxpagesize/1024.0) ) as &quot;Allocated MB&quot;

from

&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;sysobjects

order by

&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;reserved_pages(db_id(),id) desc

go
&lt;/pre&gt;
&lt;br /&gt;
&lt;b&gt;Top 10 largest tables in a database by used allocated space:
&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;pre&gt;select

top 10

&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;name,

&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;used_pages(db_id(),id)

/(1024.0 / (@@maxpagesize/1024.0) ) as &quot;Used MB&quot;

from

&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;sysobjects

order by

&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;used_pages(db_id(),id)(db_id(),id) desc

go&amp;nbsp;&lt;/pre&gt;
**These are not my own queries..Credit goes to &lt;b&gt;Bret Halford&lt;/b&gt; on sybase forums.
&lt;/div&gt;</description><link>http://sybaseadmin.blogspot.com/2011/12/top-10-large-tables-in-database.html</link><author>noreply@blogger.com (Sri)</author><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-1735402693220976337</guid><pubDate>Thu, 22 Dec 2011 18:28:00 +0000</pubDate><atom:updated>2011-12-23T00:02:30.938+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><category domain="http://www.blogger.com/atom/ns#">login</category><category domain="http://www.blogger.com/atom/ns#">sa</category><category domain="http://www.blogger.com/atom/ns#">sybase</category><title>sa Login locked?</title><description>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;
Add &quot;-T4044&quot; to the command line in the RUN_server file.&lt;br /&gt;
This will&amp;nbsp; allow you to log in as &#39;sa&#39;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;&lt;/div&gt;</description><link>http://sybaseadmin.blogspot.com/2011/12/sa-login-locked.html</link><author>noreply@blogger.com (Sri)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-7276907337170998784</guid><pubDate>Tue, 20 Dec 2011 13:28:00 +0000</pubDate><atom:updated>2011-12-20T18:58:27.219+05:30</atom:updated><title>Hi to All</title><description>Hi,
All will get timely updates on this blog!!!</description><link>http://sybaseadmin.blogspot.com/2011/12/hi-to-all.html</link><author>noreply@blogger.com (Sri)</author><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-7273101293692409102</guid><pubDate>Wed, 26 Jan 2011 04:09:00 +0000</pubDate><atom:updated>2011-01-26T09:39:12.195+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><category domain="http://www.blogger.com/atom/ns#">storage</category><title>Maximum device size for ASE 12.5 and ASE 15.0</title><description>Up to ASE 12.5.x the maximum device size is 32GB (provided&lt;br /&gt;
that the OS knows how to handle large [&gt;2GB] files) because&lt;br /&gt;
of the way the device number is encoded in the sysdevices&lt;br /&gt;
table (i.e. only 24 bits are available to describe the file&lt;br /&gt;
itself).&lt;br /&gt;
&lt;br /&gt;
In ASE 15 this limit has been lifted.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
ASE-15 device and database limits per server are as follow:&lt;br /&gt;
&lt;br /&gt;
- device size limit:  4 terabytes per device&lt;br /&gt;
- server limit:  2 billion logical devices per server&lt;br /&gt;
- database size limit:  32 terabytes per database&lt;br /&gt;
- server limit:  32767 databases per server&lt;br /&gt;
&lt;br /&gt;
So, maximum storage per ASE server is over one million terabytes (32TB x&lt;br /&gt;
32767).</description><link>http://sybaseadmin.blogspot.com/2011/01/maximum-device-size-for-ase-125-and-ase.html</link><author>noreply@blogger.com (Sri)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-4352773200022303452</guid><pubDate>Mon, 24 Jan 2011 17:16:00 +0000</pubDate><atom:updated>2011-01-24T22:46:57.565+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><category domain="http://www.blogger.com/atom/ns#">backup</category><category domain="http://www.blogger.com/atom/ns#">sybase</category><title>dump database three phases</title><description>The dump database command makes a copy of the entire &lt;br /&gt;
database, including both the data and the transaction log. &lt;br /&gt;
dump database does not truncate the log. &lt;br /&gt;
dump database allows dynamic dumps. Users can continue to &lt;br /&gt;
make changes to the database while the dump takes place. &lt;br /&gt;
This makes it convenient to back up databases on a regular &lt;br /&gt;
basis. &lt;br /&gt;
dump database executes in three phases. A progress message &lt;br /&gt;
informs you when each phase completes. When the dump is &lt;br /&gt;
finished, it reflects all changes that were made during its &lt;br /&gt;
execution, except for those initiated during phase 3.&quot; &lt;br /&gt;
&lt;br /&gt;
Phase 1 &lt;br /&gt;
* Phase 1 is the DBPAGES phase &lt;br /&gt;
* The Backup Server scans and dumps all the allocated &lt;br /&gt;
pages (both data and log pages) for the given database, &lt;br /&gt;
without checking to see whether any of the pages were &lt;br /&gt;
updated while this phase is going on. &lt;br /&gt;
&lt;br /&gt;
Phase 2 &lt;br /&gt;
* Phase 2 is the FLUSHPAGES phase: &lt;br /&gt;
* All the data pages that were modified during but not &lt;br /&gt;
logged in phase 1 (for example, a fast bcp) are dumped. &lt;br /&gt;
* The dump instant is the end of this phase. Recovery &lt;br /&gt;
restores the database to the state after phase 2. &lt;br /&gt;
&lt;br /&gt;
Phase 3 &lt;br /&gt;
* Phase 3 is the SCANLOGPAGES phase: &lt;br /&gt;
* The log pages are dumped again to capture &lt;br /&gt;
up-to-the-minute changes. &lt;br /&gt;
* dump transaction has only one phase: the SCANLOGPAGES &lt;br /&gt;
phase.</description><link>http://sybaseadmin.blogspot.com/2011/01/dump-database-three-phases.html</link><author>noreply@blogger.com (Sri)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-1756537618817357099</guid><pubDate>Mon, 24 Jan 2011 15:21:00 +0000</pubDate><atom:updated>2011-01-24T20:51:58.197+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><category domain="http://www.blogger.com/atom/ns#">sybase</category><category domain="http://www.blogger.com/atom/ns#">systemtables</category><category domain="http://www.blogger.com/atom/ns#">tips</category><title>how to get host/port,host name,server name,and db name in syabse</title><description>&lt;pre&gt;select address_info as &quot;host/port&quot;
      ,host_name() as &quot;hostname&quot;
      ,@@servername as &quot;servername&quot;
      ,db_name() &quot;current_dbname&quot;
from master..syslisteners&lt;/pre&gt;</description><link>http://sybaseadmin.blogspot.com/2011/01/how-to-get-hostporthost-nameserver.html</link><author>noreply@blogger.com (Sri)</author><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-7267288740103285201</guid><pubDate>Mon, 24 Jan 2011 12:27:00 +0000</pubDate><atom:updated>2011-01-24T17:59:22.582+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><category domain="http://www.blogger.com/atom/ns#">storage</category><category domain="http://www.blogger.com/atom/ns#">sybase</category><category domain="http://www.blogger.com/atom/ns#">tips</category><title>Use of &quot;with overrride&quot; option in database creation</title><description>&lt;div dir=&quot;ltr&quot; style=&quot;text-align: left;&quot; trbidi=&quot;on&quot;&gt;&lt;br /&gt;
Suppose we  have a device, test_dev and you wish to create a database&lt;br /&gt;
with data and log on it.&lt;br /&gt;
&lt;br /&gt;
&lt;pre&gt;create database testdb1
 on test_dev = 100
 log on test_dev = 20
 with override&lt;/pre&gt;&lt;br /&gt;
You now have distinct data and log segments on the same device.&lt;br /&gt;
You can dump this log as usual with dump tran.&lt;br /&gt;
&lt;br /&gt;
The log is always on it&#39;s own segment (the &quot;log&quot; segment).&lt;br /&gt;
The problem with dumping the tran log comes when the log segment is mixed with any other&lt;br /&gt;
kind of segment on the same fragment &lt;br /&gt;
(yielding a sysusages segmap that is something other than &quot;4&quot;)&lt;br /&gt;
&lt;/div&gt;</description><link>http://sybaseadmin.blogspot.com/2011/01/suppose-we-have-device-testdev-and-you.html</link><author>noreply@blogger.com (Sri)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-6050269602978152989</guid><pubDate>Wed, 19 Jan 2011 16:46:00 +0000</pubDate><atom:updated>2011-01-19T22:16:53.047+05:30</atom:updated><title>dsync,direct io</title><description>The directio and dsync parameters are mutually exclusive. If a device has dsync set to “true,” you cannot set&lt;br /&gt;
directio to “true” for this device. To enable directio for a device, you must first reset dsync to “false.”&lt;br /&gt;
Direct I/O is always the preferred way.&lt;br /&gt;
dsync only applies to operating system files (meaning that it has no&amp;nbsp;effect on &quot;raw&quot; devices used as Sybase disk devices)</description><link>http://sybaseadmin.blogspot.com/2011/01/dsyncdirect-io.html</link><author>noreply@blogger.com (Sri)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-616433446300971325</guid><pubDate>Sun, 29 Aug 2010 05:52:00 +0000</pubDate><atom:updated>2010-08-29T11:38:08.249+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">book</category><category domain="http://www.blogger.com/atom/ns#">free</category><category domain="http://www.blogger.com/atom/ns#">replication</category><title>Get a free copy of &quot;Replication For Dummies&quot;</title><description>Click the following link ..to get a free copy of &amp;nbsp;&quot;Replication For Dummies&quot;&lt;br /&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; text-align: center;&quot;&gt;&lt;a href=&quot;http://img.en25.com/eloquaimages/clients/sybase/%7Bfcce647b-c466-4cd7-8aae-3bae831e0dc7%7D_replicationserver_header.jpg&quot; imageanchor=&quot;1&quot; style=&quot;margin-left: 1em; margin-right: 1em;&quot;&gt;&lt;img border=&quot;0&quot; height=&quot;56&quot; src=&quot;http://img.en25.com/eloquaimages/clients/sybase/%7Bfcce647b-c466-4cd7-8aae-3bae831e0dc7%7D_replicationserver_header.jpg&quot; width=&quot;320&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;
&lt;br /&gt;
&lt;tr&gt;&lt;td id=&quot;tdUrl&quot; style=&quot;font-size: 17px; text-align: right; white-space: nowrap;&quot;&gt;http://goo.gl/8oEF&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;/td&gt;&lt;/tr&gt;</description><link>http://sybaseadmin.blogspot.com/2010/08/get-free-copy-of-replication-for.html</link><author>noreply@blogger.com (Sri)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-2102676903190065810</guid><pubDate>Mon, 17 Aug 2009 16:01:00 +0000</pubDate><atom:updated>2009-08-18T11:01:56.995+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><category domain="http://www.blogger.com/atom/ns#">sybase</category><title>Clustered,Non-clustered Indexes</title><description>&lt;b&gt;Heap&lt;/b&gt; = the data in a table, rows in chronological (insert) order&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Index &lt;/b&gt;= B-Tree structure of keys, used to speed up the access to data rows.&lt;br /&gt;Except for APL/CI, it is detached (separate allocation) from the heap.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Clustered&lt;/b&gt; = A special type of Index for APL tables only; where the Index is &#39;clustered&#39; with the data; the leaf-level of the Index is the row (and therefore every access to data is one less than with a Nonclustered index).____Not available for DPL/DRL&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Nonclustered &lt;/b&gt;= the ordinary Index, any index other than Clustered, detached from the Heap.&lt;br /&gt;For performnce reasons, these should be placed on a different segment to the Heap or CI.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Placement :&lt;/b&gt; A special form of Nonclustered, the attempt to provide a semblance of &#39;clustering&#39; for DPL/DRL tables only.  Lives on the same segment as the Heap.  The physical order of rows is attempted (it exists after a fresh create_index or reorg_rebuild, but it is lost after a few insert/deletes)&lt;br /&gt;&lt;br /&gt;&lt;div style=&quot;color: red;&quot;&gt;**The term Clustered when used with DPL/DRL, is incorrect**.   &lt;/div&gt;&lt;div style=&quot;color: red;&quot;&gt;&lt;/div&gt;&lt;div style=&quot;color: red;&quot;&gt;**Unfortunately the manuals use the incorrect term**&lt;/div&gt;&lt;br /&gt;&lt;b&gt;Unique&lt;/b&gt; = the indexed column(s) uniquely identify a single row. Prevents another row with the same values as the indexed column(s) being inserted.&lt;br /&gt;&lt;br /&gt;&lt;b&gt;Nonunique&lt;/b&gt; = the indexed column(s) identify more than one row.&lt;br /&gt;&lt;br /&gt;Composite Key (not composite index) = The Key has more than one column.&lt;br /&gt;&lt;br /&gt;APL/DPL/DRL are lockschems for the tables.&lt;br /&gt;&lt;br /&gt;Credit goes to &lt;b&gt;Derek Asirvadem&lt;/b&gt; for his clear explanation about indexes on sybase forums...</description><link>http://sybaseadmin.blogspot.com/2009/08/clusterednon-clustered-indexes.html</link><author>noreply@blogger.com (Sri)</author><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-143946476010935069</guid><pubDate>Thu, 13 Aug 2009 13:53:00 +0000</pubDate><atom:updated>2009-08-13T19:25:22.093+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><title>ASE 15.0 Release Schedule and CR list Information</title><description>In the following link you will CR list information and Release terminology&lt;br /&gt;
Have a look &lt;a href=&quot;http://www.sybase.com/detail?id=1038641&quot;&gt;at this link&lt;/a&gt;</description><link>http://sybaseadmin.blogspot.com/2009/08/ase-150-release-schedule-and-cr-list.html</link><author>noreply@blogger.com (Sri)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-5787693412618668854</guid><pubDate>Mon, 27 Jul 2009 17:18:00 +0000</pubDate><atom:updated>2009-07-27T22:52:35.324+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><category domain="http://www.blogger.com/atom/ns#">systemtables</category><title>Zombie processes in ASE</title><description>&lt;div xmlns=&#39;http://www.w3.org/1999/xhtml&#39;&gt;When you do not have the row in sysprocesses but you do have in&lt;br/&gt;syslocks that is zombie  lock ( i.e. phantom lock )&lt;br/&gt;You will need to either recycle ASE server or use  dbcc . If you are&lt;br/&gt;using  ASE 12.5.4 or later version , you can try using &#39;dbcc&lt;br/&gt;lock_release&#39;&lt;br/&gt;&lt;br/&gt;A phantom [lock] is when there is an entry in syslocks for&lt;br/&gt;a spid,  but the spid does not exist in sysobjects (phantoms&lt;br/&gt;have no body, just cast a shadow).  Phantom locks are usually&lt;br/&gt;due to bugs in process cleanup in the ASE.  &lt;br/&gt;&lt;br/&gt;&lt;/div&gt;</description><link>http://sybaseadmin.blogspot.com/2009/07/zombie-processes-in-ase_27.html</link><author>noreply@blogger.com (Sri)</author><thr:total>1</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-3169883321813408398</guid><pubDate>Fri, 17 Jul 2009 03:45:00 +0000</pubDate><atom:updated>2009-07-27T22:36:45.241+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">sql</category><category domain="http://www.blogger.com/atom/ns#">systemtables</category><title>Displaying access information from sysprotects</title><description>&lt;div xmlns=&quot;http://www.w3.org/1999/xhtml&quot;&gt;list privileges for each user&lt;br /&gt;&lt;br /&gt; &lt;pre&gt;select u.name,v.name&lt;br /&gt; from sysprotects p, master.dbo.spt_values v, sysusers u&lt;br /&gt; where p.uid=u.uid&lt;br /&gt; and p.action=v.number&lt;br /&gt; and p.protecttype=1&lt;br /&gt; and v.type = &#39;T&#39;&lt;br /&gt; and u.name!= &#39;dbo&#39;&lt;br /&gt; go&lt;/pre&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/div&gt;</description><link>http://sybaseadmin.blogspot.com/2009/07/displaying-access-information-from.html</link><author>noreply@blogger.com (Sri)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-3891899776899191716</guid><pubDate>Sun, 28 Jun 2009 14:36:00 +0000</pubDate><atom:updated>2009-07-28T08:57:49.738+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><title>Maximum Addressable Shared Memory in ASE 12.0.x and 12.5.x</title><description>&lt;div xmlns=&#39;http://www.w3.org/1999/xhtml&#39;&gt;The following table lists, by platform, the maximum size of shared memory for Adaptive Server Enterprise (ASE) 12.0.x and 12.5.x: &lt;br /&gt;
   &lt;table width=&#39;95%&#39; border=&#39;1&#39;&gt;&lt;tbody&gt;
&lt;tr&gt;    &lt;th&gt;&lt;strong&gt;Platform&lt;/strong&gt;&lt;/th&gt;&lt;th&gt;32-bit ASE&lt;/th&gt;&lt;th&gt;64-bit ASE&lt;/th&gt;&lt;th&gt;&lt;strong&gt;Comments&lt;/strong&gt;&lt;/th&gt;   &lt;/tr&gt;
&lt;tr&gt;    &lt;td&gt;HP-UX 11.x (PA-RISC processor)&lt;/td&gt;    &lt;td&gt;2.75 GB &lt;/td&gt;    &lt;td&gt;16 EB&lt;/td&gt;    &lt;td&gt; &lt;/td&gt;   &lt;/tr&gt;
&lt;tr&gt;    &lt;td&gt;HP-UX 11.x (Itanium2 processor)&lt;/td&gt;    &lt;td&gt;N/A&lt;/td&gt;    &lt;td&gt;16 EB&lt;/td&gt;    &lt;td&gt;Available Q4 2003&lt;/td&gt;   &lt;/tr&gt;
&lt;tr&gt;    &lt;td&gt;HP Tru64 5.x&lt;/td&gt;    &lt;td&gt;N/A&lt;/td&gt;    &lt;td&gt;16 EB&lt;/td&gt;    &lt;td&gt; &lt;/td&gt;   &lt;/tr&gt;
&lt;tr&gt;    &lt;td&gt;IBM AIX 5.x&lt;/td&gt;    &lt;td&gt;2.75 GB &lt;/td&gt;    &lt;td&gt;16 EB&lt;/td&gt;    &lt;td&gt; &lt;/td&gt;   &lt;/tr&gt;
&lt;tr&gt;    &lt;td&gt;SGI IRIX 6.x&lt;/td&gt;    &lt;td&gt;4 GB&lt;/td&gt;    &lt;td&gt;16 EB&lt;/td&gt;    &lt;td&gt; &lt;/td&gt;   &lt;/tr&gt;
&lt;tr&gt;    &lt;td&gt;Sun Solaris 8 (sparc processor) &lt;/td&gt;    &lt;td&gt;3.78 GB&lt;/td&gt;    &lt;td&gt;16 EB&lt;/td&gt;    &lt;td&gt; &lt;/td&gt;   &lt;/tr&gt;
&lt;tr&gt;    &lt;td&gt;Sun Solaris 8 (Intel x86 processor)&lt;/td&gt;    &lt;td&gt;3.75 GB &lt;/td&gt;    &lt;td&gt;N/A&lt;/td&gt;    &lt;td&gt; &lt;/td&gt;   &lt;/tr&gt;
&lt;tr&gt;    &lt;td&gt;Windows 2000, 2003 and XP&lt;/td&gt;    &lt;td&gt;~1.75 GB * &lt;/td&gt;    &lt;td&gt;N/A&lt;/td&gt;    &lt;td&gt;See note below&lt;/td&gt;   &lt;/tr&gt;
&lt;tr&gt;    &lt;td&gt;Red Hat Enterprise Linux &lt;br /&gt;
(Intel x86 processor) &lt;/td&gt;    &lt;td&gt;2.7 GB&lt;/td&gt;    &lt;td&gt;N/A&lt;/td&gt;    &lt;td&gt; &lt;/td&gt;   &lt;/tr&gt;
&lt;tr&gt;    &lt;td&gt;Red Hat Enterprise Linux &lt;br /&gt;
(Itanium2 processor)&lt;/td&gt;    &lt;td&gt;N/A&lt;/td&gt;    &lt;td&gt;16 EB&lt;/td&gt;    &lt;td&gt;Available Q4 2003&lt;/td&gt;   &lt;/tr&gt;
&lt;tr&gt;    &lt;td&gt;Mac OSX &lt;/td&gt;    &lt;td&gt;2 GB &lt;/td&gt;    &lt;td&gt;N/A&lt;/td&gt;    &lt;td&gt; &lt;/td&gt;   &lt;/tr&gt;
&lt;/tbody&gt; &lt;/table&gt;&lt;p&gt;&lt;em&gt;Notes:&lt;/em&gt;  &lt;/p&gt;&lt;ul&gt;&lt;li&gt;One Exabyte equals 2^60, or 1024 PetaByte. 16 EB is a theoretical limit; in practice, the actual value is limited by the total memory available on the system. ASE has been tested with a maximum of 256 GB of shared memory.&lt;/li&gt;
&lt;/ul&gt;&lt;p&gt;  &lt;/p&gt;&lt;span id=&quot;therest&quot;&gt;&lt;br /&gt;
&lt;ul&gt;&lt;li&gt; * The maximum size of shared memory for 32-bit windows is approximately 1.75GB. This value can vary depending on the size of the ASE code and associated dlls, which also occupies the 2GB application space. You may need to reduce the max memory value in order to start ASE.&lt;br /&gt;
&lt;br /&gt;
&lt;/li&gt;
&lt;li&gt;On some Windows 32-bit OS, you can use the &lt;strong&gt;/3GB&lt;/strong&gt; option to boot the operating system; this allows ASE to use upto 3 GB shared memory. Check your specific OS version to see if it allows the /3GB option.&lt;br /&gt;
&lt;br /&gt;
&lt;/li&gt;
&lt;li&gt;Each operating system has a default maximum shared-memory segment (for example, &lt;em&gt;shm-max&lt;/em&gt; on HP Tru64). Check that the operating system is configured to allow the allocation of a shared-memory segment at least as large as ASE&#39;s &lt;strong&gt;total memory&lt;/strong&gt; (12.0.x) or &lt;strong&gt;max memory&lt;/strong&gt; (12.5.x) configuration parameter. See your platform&#39;s &lt;em&gt;Installation Guide for Adaptive Server Enterprise&lt;/em&gt; for details.&lt;/li&gt;
&lt;p&gt;ASE 12.5 changes how memory is allocated, resulting in changes to memory-related configuration parameters and introduction of new parameters. Be sure you understand the new memory configurations in ASE 12.5 when modifying server and/or operating system memory parameters. See &lt;em&gt;What&#39;s New in Adaptive Server Enterprise?&lt;/em&gt; and the &lt;em&gt;System Administration Guide&lt;/em&gt; for details.   &lt;/p&gt;&lt;/ul&gt;&lt;br /&gt;
&lt;/span&gt;&lt;br /&gt;
&lt;/div&gt;</description><link>http://sybaseadmin.blogspot.com/2009/06/maximum-addressable-shared-memory-in.html</link><author>noreply@blogger.com (Sri)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-98260774585631656</guid><pubDate>Sat, 27 Jun 2009 17:18:00 +0000</pubDate><atom:updated>2009-07-27T22:42:31.713+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">ase</category><title>What is &amp;#39;Compatibility Mode&amp;#39; in ASE 15.0.3 ESD#1?</title><description>&lt;div xmlns=&#39;http://www.w3.org/1999/xhtml&#39;&gt;At the end of March 2009, version 15.0.3 ESD#1 of Sybase Adaptive Server Enterprise (ASE) was released. This ESD&lt;br/&gt;contained a new feature named &#39;compatibility mode&#39;.&lt;br/&gt;&lt;br/&gt;Compatibility mode is a query processing enhancement in ASE 15.0.3 ESD#1 that allows qualifying T‐SQL queries to&lt;br/&gt;be processed with a method of query optimization and query execution very similar to that used in ASE 12.5,&lt;br/&gt;instead of using the ASE 15 query processing algorithms.&lt;br/&gt;&lt;br/&gt;Compatibility mode can be enabled server‐wide for the entire ASE server, as well as for an individual session only.&lt;br/&gt;By default, compatibility mode is disabled. To enable it on server level, set the configuration parameter &#39;enable&lt;br/&gt;compatibility mode&#39; to 1 (when set to 0, it is disabled):&lt;br/&gt;&lt;br/&gt;         &lt;pre&gt;&lt;b&gt;sp_configure &#39;enable compatibility mode&#39;, 1&lt;/b&gt;&lt;br/&gt;&lt;br/&gt;&lt;/pre&gt;To override the server‐wide compatibility mode setting for an individual session, use this syntax:&lt;br/&gt;&lt;br/&gt;      &lt;pre&gt;&lt;b&gt;  set compatibility_mode on&lt;/b&gt;&lt;/pre&gt;&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;&lt;/div&gt;</description><link>http://sybaseadmin.blogspot.com/2009/06/what-is-mode.html</link><author>noreply@blogger.com (Sri)</author><thr:total>0</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-4718228601706244075</guid><pubDate>Mon, 18 May 2009 14:43:00 +0000</pubDate><atom:updated>2009-07-27T22:44:36.869+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">tools</category><title>How to convert a sybase backtrack dump to native dump</title><description>&lt;p&gt; We need to have the sql bactrack installed and configured on the server. The below command on execution will change the sql-backtrack dump to sybase native dump&lt;/p&gt; &lt;pre&gt; &lt;p&gt; &lt;br /&gt;&lt;strong&gt;dtsload -physical -from &quot;/$PATH/master-0.11-04-2005.20:02:58_23434&quot; -sybase_dump master.dmp&lt;/strong&gt;&lt;/p&gt;&lt;/pre&gt;</description><link>http://sybaseadmin.blogspot.com/2009/05/how-to-convert-sybase-backtrack-dump-to.html</link><author>noreply@blogger.com (Sri)</author><thr:total>2</thr:total></item><item><guid isPermaLink="false">tag:blogger.com,1999:blog-6510244423305214811.post-2696590761869584319</guid><pubDate>Tue, 17 Feb 2009 07:55:00 +0000</pubDate><atom:updated>2009-07-27T22:43:34.090+05:30</atom:updated><category domain="http://www.blogger.com/atom/ns#">tips</category><title>How know when your ASE server was started??</title><description># In ASE 12.5, the server boot time has been captured in loggedindatetime of sysprocesses for the internal system processes:&lt;br /&gt;&lt;p&gt;&lt;br /&gt;&lt;pre&gt;select min(loggedindatetime)&lt;br /&gt;from master..sysprocesses where suid=0&lt;br /&gt;&lt;/pre&gt;&lt;br /&gt;# In ASE 12.5.0.1, it&#39;s even simpler:&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;pre&gt;select @@boottime&lt;/pre&gt;&lt;br /&gt;&lt;br /&gt;The static global variable @@boottime is undocumented, but happens to be identical to sysdatabases.crdate for tempdb. &lt;/p&gt;</description><link>http://sybaseadmin.blogspot.com/2009/02/how-know-when-your-ase-server-was.html</link><author>noreply@blogger.com (Sri)</author><thr:total>0</thr:total></item></channel></rss>