Sybase World

Manually Rebuilding Adaptive Server with bcp Manually rebuilding Adaptive Server with bcp and server building utilities enables you to create a new master device/configuration block and preserve system tables. As of version 12.5, master devices and servers are built with the dataserver (Unix) and sqlsrvr (Windows) programs. In pre-12.5 versions, they are built with buildmaster. Some of the most common uses for a manual rebuild are when: • The master device has no more available space. You can migrate the system table information to a new, larger master device while retaining all current data on the original devices. • Restoring the master device resulted in 605 errors due to an incorrect sysusages table. You can use trace flags, along with the bcp and server build steps, to get the information needed for a rebuild. • No backup of the master database exists. The old master database is accessible, although it is not runnable. You can migrate the system information to a new master databas...

Rplication server internals ------------------------------- Functioning of all threads ------------------------------- 1> Rep Agent --------------- a> Scans transaction log PDB b> Converts log records to log transfer language and send to Inbound queues c> moves the secondary truncation point d> verifies correct object schema 2> Stable queue manager ----------------------- a> Used to manage process of reading/writing/deleting messages on stable device 3> stable queue transaction --------------------------- a> Passes stable device messages to clients in commit order * Client includes DIST and DSI threads * SQT cache size ---------------- a> Each IBQ consumes sqt_max_cache_size b> Each DSI also takes sqt_max_cache_size 4> distributor (DIST) --------------------- a> Calls SQT and SQM to read the IBQ in commit order b> Destination will be an OBQ c> Makes calls to 3 libraries 1> Subscription resolution engine 2> Transaction delivery ...

Some hidden things about ASE Different States of SLEEP When all processes are shown as SLEEPING by sp_who except the one, which issued the sp_who command, how can a user tell the difference between hangings versus running processes? Definitions In pre-4.9.2 SQL Servers, the output of sp_who could be difficult to interpret. Processes showed only one type of SLEEP status, "sleeping". In System 10, and 4.9.2 Rollup 2115 and above, sp_who shows four types of sleep along with the other possible statuses: Value Meaning Infected The server erred with a stack trace, and the process got an error that would normally kill it. The process is infected instead of killed. Background This process is in the background recv sleep The process is waiting for input from the client Send sleep The process is waiting for a write to the client to complete alarm sleep The process is waiting for an alarm (usually means the process is waiting for a wait for command to complete). Lock sleep The process i...

Recovery Of Master In ASE Introduction This document describes the disaster recovery procedure to follow when the master database or the master device in ASE 12.0.x has been lost and the server was upgraded from a pre-12.0 server. Changes in Adaptive Server Enterprise 12.0 make it necessary to use this procedure, instead of the standard procedures described in the System Administration Guide or the Troubleshooting & Error Messages Guide, for a server upgraded from pre-12.0. Two scenarios are covered in separate sections: • The master device is lost • The master database is lost but the master device is intact. This discussion assumes that you did not alter any databases on the master device. Recovering from that scenario is beyond the scope of this document; contact Sybase Technical Support for assistance. For ASE 12.5.x servers upgraded from a previous version, see the disaster recovery procedure described in TechNote 1028123, Recovering an Upgraded Master Device and master Databa...

Introduction Undocumented DBCC commands: • DBCC BUFFER • DBCC BYTES • DBCC DBINFO • DBCC DBTABLE • DBCC DES • DBCC HELP • DBCC IND • DBCC LOG • DBCC PAGE • DBCC PROCBUF • DBCC PRTIPAGE • DBCC PSS • DBCC RESOURCE • DBCC TAB Literature Introduction In this article I want to tell you about some useful undocumented DBCC commands, and how you can use these commands in SQL Server 7.0 for administering and monitoring. DBCC is an abbreviation of a DataBase Consistency Checker. This is the description of DBCC from SQL Server Books Online: A statement used to check the logical and physical consistency of a database, check memory usage, decrease the size of a database, check performance statistics, and so on. Database consistency checker (DBCC) ensures the physical and logical consistency of a database, but is not corrective. Undocumented DBCC commands 1. DBCC BUFFER This command can be used to print buffer headers and pages from the buffer cache. Syntax: dbcc buffer ([dbid|dbname] ...

dbcc Description Database Consistency Checker (dbcc) checks the logical and physical consistency of a database and provides statistics, planning, and repair functionality. Syntax dbcc addtempdb( dbid | databbase_name ) dbcc checkalloc [(database_name [, fix | nofix])] dbcc checkcatalog [(database_name)] dbcc checkdb [(database_name [, skip_ncindex])] dbcc checkstorage [(database_name)] dbcc checktable({table_name | table_id}[, skip_ncindex]) dbcc checkverify [(database_name)] dbcc complete_xact (xid, {"commit" | "rollback"}) dbcc forget_xact (xid) dbcc dbrepair (database_name, dropdb) dbcc engine( {offline , [enginenum] | "online" }) dbcc fix_text ({table_name | table_id}) dbcc indexalloc ({table_name | table_id}, index_id [, {full | optimized | fast | null} [, fix | nofix]]) dbcc pravailabletempdbs dbcc rebuild_text (table [, column [, text_page_number]]) dbcc reindex ({table_name | table_id}) dbcc tablealloc ({table_name | table_id} [, {fu...

Proxy_Table…………….Amol P Ingle Proxy tables Proxy tables are the key to location transparency. A proxy table is a local table containing metadata which points to a remote object. The remote table is mapped to the proxy table to make it appear as if it were a local table. If there are two servers such as Server A and Server B and user want to create proxy table from server A to Server B. Then please do the following Steps: In Server A: 1. Make the entry of interfaces file of server B into server A. 2. Add server sp_addserver “Server B” 3. Create one table in master/or any db for testing. 4. suppose create table amol. 5 Insert Values Into table amol 6. Check with the select command 1> select * from amol 2> go name -------------------- amol Login into server B 1. Make the entry of interfaces file of server A into server B. 2. Add server sp_addserver “Server A” 3. Create table amol at "Server_A.db_name.dbo.amol" go 4. Check with the select command 1> ...