The staff at SQLServerCentral.com really appreciates your support and contributions to the community. We are always looking to improve things here and we have made a couple changes to the way our email system works.
2005-01-11
2,988 reads
Andrew Zanevsky shares his trace-scrubbing procedures that make it easy for you to handle large trace files and aggregate transactions by type–even when captured T-SQL code has variations.
SQL Server Profiler is a veritable treasure trove when it comes to helping DBAs optimize their T-SQL code. But, the surfeit of riches (I'm reminded of the Arabian Nights tale of Aladdin) can be overwhelming. I recently had one of those "sinking" feelings when I first tried to make sense of the enormous amount of data collected by traces on a client's servers. At this particular client, the online transactions processing system executes more than 4 million database transactions per hour. That means that even a 30-minute trace that captures "SQL Batch Completed" events results in a table with 2 million rows. Of course, it's simply impractical to process so many records without some automation, and even selecting the longest or most expensive transactions doesn't necessarily help in identifying bottlenecks. After all, short transactions can be the culprits of poor performance when executed thousands of times per minute.
2005-01-11
2,003 reads
The Northern Virginia SQL Server Users group serves the Maryland and Virginia areas around Washinton DC. The group is being restarted by Brian Moran and Jeremy Kadlec. If you're in the area, please read about this announcement and give them your support.
2005-01-10
2,529 reads
Many thanks from Andy, Brian, and Steve to everyone for their participation and efforts in building the best SQL Server site and the best community on the Internet. In appreciation of their efforts, we've given away a few gifts to some random members.
2005-01-10
2,479 reads
Trey Johnson, a PASS board member and a senior business intelligence consultant, is doing a webcast on Tuesday. Join him for a great talk getting a business intelligence system up and successful in your environment.
2005-01-10
2,668 reads
Ken Henderson explains how to use PSSDiag, a diagnostics collection tool for SQL Server. PSSDiag is one of several Microsoft Product Support Services tools recently released to the Web that are now available for personal use. (26 printed pages)
2005-01-10
1,490 reads
Transactional replication is a type of replication provided by SQL Server 2000 that allows data modifications to be propagated incrementally between servers in a distributed environment.
2005-01-07
3,834 reads
This article contains information about the bugs that are fixed by Microsoft SQL Server 2000 Service Pack 4 Beta. (SP4).
2005-01-06
6,292 reads
If you are running Microsoft SQL Server databases to support critical enterprise applications, you are part of a growing trend.
2005-01-06
1,972 reads
SwisSQL develops products for SQL Server and other RDBMSs that ease the migration between platforms. They have provided us with a case study to show how you can easily move data from an Oracle system to the premier database platform, SQL Server. Check out this case study of how one of the ERP vendors used their product to migrate their code.
2005-01-05
3,109 reads
By ChrisJenkins
Have you been thinking about migrating your reporting to Microsoft Fabric or Snowflake but...
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers