How many times have I needed to do this for reporting purposes? I remember coming up with some convoluted process that did the trick but was in no way as elegant as the solution suggested in this post (or the one in the comments).
You might find the two following posts interesting if you’re dealing with vast amounts of data: Kimball ETL screening Data profiling with T-SQL
Posted for future reference. This article by Jeff Smith “covers different ways to create sequence numbers. It starts with the basic identity and GUIDs and quickly moves to much more complicated sequence numbers including those with auto-incrementing mixed letters and numbers such as “A0001″, etc.”
Thinking of migrating the database portion of your Access-based (JET SQL) solution to SQL Server (T-SQL)? Well Jeff Smith just posted a quick MS Access (JET SQL) to SQL Server (T-SQL) Cheatsheet to help you in this process.
Stephen Swoyer has published a brief analysis at TDWI on why the SQL Server installed base seems to be growing relatively slowly. Bottom line: the learning curve is steep and corporations cannot easily replace prior SQL Server versions running mission-critical applications.You’ve got to love his quote of Adam Machanic (SQL Server MVP) saying that “comparingContinue reading “The (Steep) SQL Server 2005 Learning Curve”