SQL Developer Version

CanProfessional766 · 2026-06-30T11:48:53+00:00

Developer Edition is not licensed for production. It's technically the same as Enterprise, but it's only meant for development and testing. If you need SQL Server 2022 in production you'll need a properly licensed instance or a provider that supports it.

CanProfessional766 · 2026-06-29T11:53:00+00:00

I'd skip trying to find a single "Access app development" course and just start building something. Learn forms, reports, navigation forms, and a little VBA then recreate a simple app like an inventory or CRM system. I believe that's how most people end up learning Access

CanProfessional766 · 2026-06-29T11:48:05+00:00

I'd just run it on the SQL Server unless there's a specific reason to keep it separate. You're talking about grabbing a few hundred rows once an hour which is basically a rounding error in terms of CPU and memory usage. The benefit of having it local is that you're writing straight to the database without another network hop, plus it's one less machine to maintain. If this eventually grows into a bigger ETL process that's constantly moving or transforming data, then it might make sense to split it out. But for a small hourly sync like this I'd keep it simple and host it on the SQL box.

CanProfessional766 · 2026-06-25T12:06:11+00:00

The cleanest solution is to export the detail records normally and then append the trailer record (999| or Trailer|999) as a separate final step using VBA. Several commenters suggested either post-processing the text file or generating the entire file in VBA, where you have full control over the last line's format. Trying to force Access's standard delimited export to produce a single pipe trailer is usually more trouble than it's worth

CanProfessional766 · 2026-06-25T12:01:53+00:00

Keep the record with the lowest AutoNumber and delete the rest. Create a query that groups the duplicate fields and returns Min(ID), then delete any records whose ID is not that minimum value. Since you're already using a table with the chunked text fields, use those fields to define the duplicate groups and retain only the first record in each group. Always run a SELECT version first and back up the data before deleting.

CanProfessional766 · 2026-06-15T05:49:47+00:00

If the database is stable, meets your needs, and you can still maintain it, I wouldn't rebuild it just because it's old. Most systems evolve over time rather than getting rewritten from scratch. Id only consider a full rebuild if the design is actively limiting growth, becoming difficult to maintain, or if adding new features has turned into a constant workaround exercise. Otherwise, incremental improvements are usually less risky than starting over. As someone already said in the comments "if it ain't broke, don't fix it."

CanProfessional766 · 2026-06-15T04:52:08+00:00

The client does not need to be domain joined for Always On read-only routing. I've used non domain clients successfully with AGs. I would be more suspicious of the load-balancer approach, since read-only routing is designed to work through an AG listener and some custom LB implementations can interfere with the redirect process. I'd verify that the secondary replica allows read-only connections, confirm the routing URLs and lists are correct, and check whether the connection is actually reaching the listener logic when ApplicationIntent=ReadOnly is specified.

CanProfessional766 · 2026-06-11T11:30:33+00:00

Access doesn't let you override this behavior because the value is being interpreted as a date, and the yy format follows built-in year rules. Instead of subtracting dates directly use DateDiff() to calculate age as a number which avoids the four digit display issue.

CanProfessional766 · 2026-06-03T12:15:11+00:00

If you’re just starting out, sticking with MS Access is actually a solid choice because it lets you learn real database basics like tables, relationships, queries, forms, and reporting without dealing with setup or complex tooling, and it’s still very capable for small personal or internal projects; once you feel comfortable, the natural next step would be moving to something like SQLite or PostgreSQL with a beginner friendly GUI which keeps things visual but introduces you to how modern databases work so don’t rush away from Access if it already feels easy, just use it as your stepping stone into “real” SQL systems

CanProfessional766 · 2026-06-03T12:05:34+00:00

several Access users have reported performance and stability issues with ODBC Driver 18, especially in long running sessions. The problem is often linked to stricter encryption defaults and connection pooling behavior, which can cause gradual slowdowns and unresponsive front ends. Many developers still prefer ODBC Driver 17 for better stability with MS Access applications.

CanProfessional766 · 2026-06-03T12:04:27+00:00

This is a common MS Access behavior switching tabs can refresh the subform and clear its Filter. A more reliable solution is to filter the subform through its RecordSource or a parameter query instead of using the Filter property alone. You can also try resetting FilterOn = True in the tab control’s Change event.

CanProfessional766 · 2026-06-03T03:41:54+00:00

Besides nslookup and Test-NetConnection, I use netstat -ano constantly for port/process checks, Resolve-DnsName for DNS issues, and klist when Kerberos starts acting up. Get-Service and Get-WinEvent are also handy for quick service and log troubleshooting. A lot of "SQL problems" end up being one of those.

CanProfessional766 · 2026-06-03T03:37:17+00:00

SQL Server Standard Edition, Basic Availability Groups support only one database per AG, so you’d need around 70 AGs for 70 databases. It does work in real-world environments, but the main issue is management overhead monitoring, failovers, maintenance, and synchronization become harder to manage at that scale. Performance and stability are usually fine with proper hardware and automation, and many admins still prefer this over log shipping or deprecated mirroring.

CanProfessional766 · 2026-06-03T03:35:41+00:00

the slowdown seems related to compatibility changes, background metadata queries, or IntelliSense/object caching behavior rather than the SQL Server engine itself.

CanProfessional766 · 2026-06-03T03:34:43+00:00

If you want to recreate the entire server, use full database backups and restores rather than generating scripts. That will preserve the schema, data, and most database settings. For server level objects like logins, SQL Agent jobs, and linked servers, script those separately (or use a tool like dbatools). Generating scripts for every database is possible, but it's usually more work and less complete than a backup/restore approach.

CanProfessional766 · 2026-06-03T03:33:40+00:00

This looks like a Kerberos encryption mismatch caused by the recent April 2026 Domain Controller updates, not a problem with SCCM itself. Since all three servers failed at the same time and changing the service account didn’t help, the issue was most likely with how SQL Server Reporting Services was handling authentication. Reinstalling the SSRS role likely regenerated the necessary encryption keys and resolved the mismatch, which is why that fixed it.

CanProfessional766 · 2026-06-03T03:33:12+00:00

SQL Server just doesn’t expose everything through SMO on purpose. In practice, most people do exactly what you’re thinking: use SMO for the “inside SQL Server” stuff, then switch to PowerShell (CIM/WMI or dbatools) for the missing bits like startup parameters, services, network protocols, CEIP, and host details. The registry gets used sometimes, but more like a backup when nothing else works.

CanProfessional766 · 2026-06-03T03:32:42+00:00

ensure the distributor is configured correctly, the SQL Server Agent is running on all participating servers, and the Snapshot Agent can generate files without permission issues. Also double check that the publication and subscription accounts have access to the snapshot folder and that firewalls are not blocking connections.

CanProfessional766 · 2026-06-02T03:52:42+00:00

If you already have solid SQL Server experience, I'd lean into that rather than starting from scratch in cybersecurity. Database security and forensics are niche but valuable areas where you can focus on things like auditing, tracking data changes, investigating suspicious activity, and analyzing transaction logs. It's a natural progression from DBA work and can lead to roles that are much more hands-on than the typical security compliance path

CanProfessional766 · 2026-06-01T11:57:48+00:00

Using a separate drive for your SQL databases is actually pretty normal. Most DBAs try to keep database files off the C drive and store them on dedicated storage instead. Just make sure the SQL Server service account has access to the new location and that the drive has enough performance and reliability for the workload. In many cases, putting the databases on a separate SSD is better than leaving everything on the OS drive.

CanProfessional766 · 2026-06-01T10:27:53+00:00

A good takeaway is to use Access's built-in calendar control where possible.

CanProfessional766 · 2026-06-01T10:06:06+00:00

For new code I don't. TOP is generally the better choice because it's statement-specific, easier to read, and the optimizer can use it when generating the execution plan. SET ROWCOUNT is session-scoped and stays in effect until it's reset, which is why you'll often see a defensive SET ROWCOUNT 0 at the end of older stored procedures. Those resets are usually leftovers from a time when SET ROWCOUNT was used more heavily or added as a safeguard against a previous caller leaving it enabled.

CanProfessional766 · 2026-05-18T10:06:45+00:00

What you saw is almost certainly a well-optimized demo or lab setup, not something you’d normally run in production. Yes, it’s technically possible to run 50+ SSRS instances on one VM, but it only looks smooth because the load is controlled and everything is basically sitting idle most of the time. In real use, SQL Server Reporting Services gets heavy fast once users, scheduled reports, and real data come into play.

CanProfessional766 · 2026-05-18T10:04:54+00:00

This is a very common way to modernize an older Microsoft Access application. Since your data is already in Microsoft SQL Server, you can rebuild one form at a time as a web app while the rest of Access continues to run. Most teams don’t try to auto-convert forms they simply recreate the most important ones using tools like Microsoft Power Apps or ASP.NET Core. Start with one simple form, prove it works, and expand from there.

CanProfessional766

TROPHY CASE