2019-11-19
411 reads
2019-11-19
411 reads
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.
2011-07-26
3,430 reads
Learn how to deliver dynamic content by building a meaningful Business Intelligence Application, utilizing only what is available on the client's desktop, when a Data Warehouse BI Application, SQL Server and SSIS/SSRS aren't an option.
2010-04-16
3,743 reads
This article gives a description of the iff() and DLookup() functions in Access 2007, and a method to converting them to SQL.
2010-03-08
10,975 reads
2009-06-25
4,442 reads
Access can offer a lot of help with missing values, but finding and generating missing values in a field of sequential values requires a bit of code. Find it here.
2009-01-23
1,912 reads
Learn how you can use Microsoft Access 2007 as a basic data mining tool for exploring your valuable data. This article illustrates how data filters, pivot graphs, queries in graphs and filters in reports can help this cause.
2009-01-16
2,832 reads
MS Access can retrieve and measure time with millisecond precision, but only with the help of a few well-known API calls and several user-defined functions.
2008-10-03
2,319 reads
In a previous tip we saw how easy it was to link to SQL Server tables from Microsoft Access. As is the case with all systems, how does Access manage the changes? What happens when you modify the structure of the underlying SQL Server table? What happens to the SQL Server table if you delete the linked table in Access? We will look at each of these situations in this tip.
2008-05-14
3,960 reads
This article series features a demo app affectionately named Something Not Entirely Unlike Access, which employs a variety of methods to obfuscate the "Accessian" features.
2007-09-06
3,753 reads
By Steve Jones
Thanks to everyone who attended my sessions today at SQL Saturday Boston 2025. I’ve...
SQL Server 2025 introduces native support for vector data types and external AI models....
By Steve Jones
Fear is fueled by a lack of imagination. The antidote to fear is not...
I'm building ETL packages in SSIS. My data comes from an OLE DB Source...
Comments posted to this topic are about the item Building AI Governance and Policies-...
Why is sql doing a full scan VS seeking on the index? I've included...
The DBCC CHECKIDENT command is used when working with identity values. I have a table with 10 rows in it that looks like this:
TravelLogID CityID StartDate EndDate 1 1 2025-01-11 2025-01-16 2 2 2025-01-11 2025-01-16 3 3 2025-01-11 2025-01-16 4 4 2025-01-11 2025-01-16 5 5 2025-01-11 2025-01-16 6 6 2025-01-11 2025-01-16 7 7 2025-01-11 2025-01-16 8 8 2025-01-11 2025-01-16 9 9 2025-01-11 2025-01-16 10 10 2025-01-11 2025-01-16The docs for DBCC CHECKIDENT say this if I run with only the table parameter: "If the current identity value for a table is less than the maximum identity value stored in the identity column, it is reset using the maximum value in the identity column. " I run this code:
DELETE dbo.TravelLog WHERE TravelLogID >= 9 GO DBCC CHECKIDENT(TravelLog, RESEED) GO INSERT dbo.TravelLog ( CityID, StartDate, EndDate ) VALUES (4, '2025-09-14', '2025-09-17') GOWhat is the identity value for the new row inserted by the insert statement above? See possible answers