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 James Serra
I’m honored to be hosting T-SQL Tuesday — edition #192. For those who may...
By Vinay Thakur
Continuing from Day 2 , we learned introduction on Generative AI and Agentic AI,...
Quite the title, so let me set the stage first. You have an Azure...
Comments posted to this topic are about the item A Quick Restore
Comments posted to this topic are about the item Guarding Against SQL Injection at...
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers