SciDB: Relational daddy answers Google, Hadoop, NoSQL. High performance access to file storage Battle of the rows Stonebraker reckons the relational staples such as logging, locking, latching and buffer management that have helped pioneer and maintain a crucial feature of databases - data integrity according to the atomicity, consistency, isolation and durability (ACID) principles - have also become its biggest burden. Processing alone to make these features work soaks up 90 per cent of a transaction's time in terms of CPU cycles, slowing performance and wasting power.
The serial inventor's answer to this particular problem was initially VoltDB. His database speeds things up by moving data into memory and using distributed data partitioning with multi-core processors and server memory. VoltDB claims to be 45 times faster than an Oracle relational database on a Dell PowerEdge R610 cluster based on Intel's Xeon 5550 with near-linear scaling on a 12-node cluster. Before VoltDB, there was Vertica.
Was Stonebraker surprised by the flames? Using the CommandBuilder to generate SQL Statements - Rad Software. Introduction The CommandBuilder class is a part of the .NET Framework. Its purpose is to automatically build SQL INSERT, UPDATE, and DELETE statements for a DataTable based on a SQL SELECT statement. It helps the developer write cleaner and more readable code by the avoiding code with embedded SQL statements. There are different CommandBuilder classes for the different native data access libraries. Use the OleDbCommandBuilder when connecting to Databases via OLEDB and the SqlDataAdapter for Microsoft SQL Server Databases. Getting started with the CommandBuilder When creating a CommandBuilder a DataAdapter is passed as a parameter to the constructor. Dim adpAccess As New OleDbDataAdapter( _ "SELECT * FROM [schemaDatabases]" , _ cnnDBAccessAuditorData) Dim cmdbAccessCmdBuilder As New OleDbCommandBuilder(adpAccess) cmdbAccessCmdBuilder.QuotePrefix = "[" cmdbAccessCmdBuilder.QuoteSuffix = "]" adpAccess.InsertCommand = cmdbAccessCmdBuilder.GetInsertCommand() adpAccess.Update(dtbschemaDatabases)
SQLDBTools. SQLDBDiff allows you : Ø Compare the structure of two SQL Server databases The following objects are supported : Tables and columns (with the possibility to respect or not columns order); Views (including their indexes and triggers); Stored procedures; User defined functions; Triggers; PK and Indexes (with the possibility to include or not statistic indexes); Relationships; CHECK Constraints; Default Constraints; UDDT; DDL Triggers (SQL 2008, 2005); Synonyms (SQL 2008, 2005); Permissions; User and Roles; Database properties; SQL Server properties.
Ø Generate schema synchronization scripts. Ø Generate a schema difference report. Ø Search an object by its name or content (text). Ø Compare many databases to the same master database in one step . With SQLDBDiff you cannot only compare two databases, but many databases to the same master database, you can save the list in XML file and avoid manual input. Ø Compare databases contents Ø Generate data synchronization scripts. Intelligent Enterprise Magazine - Celko (intelligententerprise.com) Replication sp_replcmds timeout (Narayana Vyas Kondreddi's SQL Server Blog) Replicating huge transactions...Mood: cool Are you replicating a table that is undergoing data modifications, that affect several thousands or even millions of rows? In that case, you could be seeing blocking on the subscribing tables, as the distribution agent tries to apply all those commands to subscriber in one big transaction. This could also affect your transaction log backup sizes on the subscribging database.
Well, I faced a similar situation today. There's hardly any information on SQL Server replication on the net. One thing to be aware of though. See "Replication Log Reader Agent Utility" in SQL Server Books Online for more information.