Part 2 of a series from Matt Perdeck on speeding up your database access. This is a great series for developers. This is based on the book ASP.NET Site Performance Secrets.
Microsoft Access is a very good database solution, but it has limits. While the portability of mdb and accdb files is convenient, there are advantages to moving to the less portable SQL Server solution. If you do have SQL Server, there's very little reason not to consider migrating your Access Databases. Not all custom-made Access applications easily lend themselves to a SQL Server solution so you'll need to do some analysis before choosing a migration path.
How to create external_access CLR assembly on remote MS SQL server, when trustworthy option is forbidden, and only SQL login is available
Steve rounds up the patch news for SQL Server this week along with a look forward to the next version of the platform.
The answers to questions from our webinar on Sandbox development.
This challenge is to generate an HTML calendar based on the data stored in a table.
Continuing from Part 1 , our Migration Checklist continues: Step 5: Update statistics It is always a good idea to update the statistics of the database that you have just installed or migrated
Come get a free day of SQL Server training in Birmingham on Jul 30, 2011.
Get three days of training in Raleigh, NC on Aug 18-20. There are free and paid options that you can read more about.
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers