This post is again in response to requests from customers who want to know how to configure Database Mirroring between instances of SQL Server 2005 in a WORKGROUP.

As you might have noticed, while configuring Database Mirroring using the GUI, it requires us to enter FQDNs of the servers; hence using the GUI, we can configure Database Mirroring between instances of SQL Server in a domain environment.

The complexity of the code within this threat is at par with that seen in Stuxnet and Duqu, arguably the two most complex pieces of malware we have analyzed to date. As with the previous two threats, this code was not likely to have been written by a single individual but by an organized, well-funded group of people working to a clear set of directives. Certain file names associated with the threat are identical to those described in an incident involving the Iranian Oil Ministry.

select
'' + char(13) + char(10)

• 'go' + char(13) + char(10)
• 'if ((select count(*) from ' + sys.schemas.name + '.[' + sys.tables.name +'])>0) '+ char(13) + char(10)
• 'begin' + char(13) + char(10)
• ' print ''---------------------'' ' + char(13) + char(10)
• ' print ''' + sys.schemas.name + '.' + sys.tables.name + ''' ' + char(13) + char(10)
• ' delete from ' + sys.schemas.name + '.[' + sys.tables.name +']'+ char(13) + char(10)
• 'end' + char(13) + char(10)
  FROM sys.tables INNER JOIN sys.schemas ON sys.tables.schema_id = sys.schemas.schema_id
  ORDER BY sys.schemas.name, sys.tables.name

Backed by stunning illustrations, David Christian narrates a complete history of the universe, from the Big Bang to the Internet, in a riveting 18 minutes. This is "Big History": an enlightening, wide-angle look at complexity, life and humanity, set against our slim share of the cosmic timeline.