The Internet Society (ISOC-AU) has recently been working on a new
project, funded by DCITA, in a consortium with auDA, AEEMA and
BuildersNet, to examine Australian readiness to implement IPv6.
As part of this exercise, organisational network planning people
(IT/Systems/Network manager or architect), are asked to complete our
Australian IPv6 readiness survey at http://www.ipv6.org.au/.
If you are at all interested in the future of the internet, please take the time to complete the survey.
Posted at 05:47 pm by ausrob2003
IPv6: The Second Conference, plus news from ICANN
Forst off a quick spot for the upcoming IPv6 conference to be held in Canberra in early December. The website (for more information) can be found at:
Last year the first IPv6 conference was held in Canberra, and was a very useful and important meeting of the minds. If you have any interest in the Internet (or Internet-enabled technology) this is THE conference for you. Book now and I'll see you there.
Now, on to other matters.. ICANN News
According to trusted UK Technology site theregister (a favourite of mine for some ten odd years or something approaching that number) apparently the US Government has finally bowed to international pressure to hand over controlling power of root domain names to an international body (ICANN, the Internet Corporation for Assigned Names and Numbers).
This has been long awaited and (although technically nothing has yet been done regarding this transition) will hopefully allow for a more balanced approach to domain name administration and to a lesser extend issues surrounding existing copyright legislation.
Lets hope such a move given ICANN more power to be authorative than the policital equivalent, the United Nations. It can't be stressed enough though, that the current structure of ICANN will need to change significantly so that it is abreast of the current issues and that it wholly represents the true demographics of the Internet, and not just the US and other western countries.
Thats all for now. Next post will be something more technical - check back soon.
Posted at 02:47 pm by ausrob2003
A Word from our sponsors: Vista Support Tool
See if your machine is capable of running the next Microsoft platform:
Windows Vista. The following is a link to a beta utility which will test
your computer's capabilities with a view to supporting Vista's core functionality:
Microsoft Australia: Tech Ed 2006
Check it out.. Tech Ed is on, and the site's up:
Main Feature: Using SMO to generate stored proc script - by your design.
First thing to do: Upgrade to SQL Server 2005. Install SP1 and then start a new C# (2.0) project.
It's so simple to create SQL Server utilities from .Net nowadays, even more so than wit SMO's
predecessor, DMO. I've written half a dozen little utilities to help with day-to-day operations,
like preparing a script containing 24 hours worth of updates to Stored Procedures.
Here's how to batch write in T-SQL the syntax of updated Stored Procs.. Read along..
You've created a C# console app, say. Add the appropriate (minimal) .NET Project References (Microsoft.SqlServer.Smo, Microsoft.SqlServer.SmoEnum and Microsoft.SqlServer.ConnectionInfo).
In code, add the appropriate using directives as so:
Now, connecting and so forth is so easy (depending on your setup). You can simply do this:
string server = "server";
_Server = new Server(server);
string db = "database";
_Database = _Server.Databases[db];
This sets up the objects you need - including authentication.
You may need additional authentication, but that is outside the
scope of this post.
Now, lets get to work..
Using generics, create storage for all Stored Procs we
want to include
List<SqlSmoObject> procedureList = new List<SqlSmoObject>();
foreach (StoredProcedure sp in _Database.StoredProcedures)
The WasCreated() function is examined in detail below.
Now, create the Scripter object
Scripter spr = new Scripter(_Server);
//Write the Create Statements
spr.Options.Permissions = true;
spr.Options.ScriptDrops = false;
spr.Options.FileName = "path and filename";
Once the options are set, we can create the
script. Notice that the Scripter will write out
the output file as an option
str = spr.Script(procedureList.ToArray());
Here is the content of the WasCreated -- used
to determine the age of the Proc. Note:
_ageComparison could be anything, though
I am using it in the context of days (1 or more)
static bool WasCreated(StoredProcedure sp)
TimeSpan ts = DateTime.Now - sp.CreateDate;
//Less than a day old
//if (ts.Days < 1)
if (ts.Days < _agecomparison)
It's that easy..
-- Now for something completely different
The Ideas Dept brings you:
Great Ideas for Windows Shell
- Instead of loading 1,000+ files all at once (inconveniently)
and blocking the UI with the "searchlight" animation, why not load the first, say, 200
files then process the rest of the files as a background thread?
- or better -
Why not load the first 50 files, then only process the rest of the folder if the user
interacts with the folder or its' contents?
Posted at 01:02 am by ausrob2003