2,738 reputation
1419
bio website alirazeghi.com
location Santa Monica
age 35
visits member for 2 years, 6 months
seen 2 days ago

Lover of all things technology, history, classic art, politics (not mud slinging), with a specific fondness of databases and long walks on the beach :P


4h
awarded  Popular Question
2d
reviewed Approve Group table records by Item than Year
Mar
27
comment Benefits of table partitioning on same disk
+1 Just note you also get more parallel SGAM threads when you partition so you get a bit more performance there, although I'd imagine in the real world it's minimal.
Mar
27
comment Sql Server Fill Factor - Restart sql server services
In addition to restarting, please also note that Fill Factor will not go back and change your old data to the new fill factor, so your indexes will remain how they are currently. Only new data coming in get's that fill factor. If you reindex or somewhere it fills up more/less it won't go back and change it back to that value.
Mar
27
comment SQL Server Differential Backup Bloat
Good question, I was going to post this to you earlier, thanks for the reminder. I've used this in the past. I'd say install it on a test server or something you can roll back because the version I had integrated pretty deep with SSMS and was a pain to get rid of. apexsql.com/sql_tools_log.aspx If you don't want to download a tool, use a script, something like this: mssqltips.com/sqlservertip/3076/… let us know if you have any more questions or if it's useful.
Mar
26
comment How to keep a live backup of an SQL server in sync?
Mirroring is still an option in SQL 2014 which was just released and mirroring is VERY straight forward to setup and fast. I'd say you're really safe going with mirroring right now until you can fully test and go with a replication method you really like. You might even be able to do read only availability groups in the near future if the price comes down. Replication is way more involved than mirroring.
Mar
25
comment SQL Server Differential Backup Bloat
Transaction log data internals are different than SQL Full/Diff backups in a few areas. First, the transaction log is written to record the absolute minimum amount of info it needs to return the affected pages back to their original state. A Diff backup in SQL Server looks at the pages that have been marked as changed from the last full backup, thus it has to copy the entire page. This is all speculation as we don't have access to your data but it could be that maybe you are just affecting a tiny bit of data in a lot of pages, or something of the sort. Is compression enabled per chance?
Mar
24
answered What causes disk space growth from Informatica load onto SQL Server?
Mar
24
answered SQL Server Differential Backup Bloat
Mar
24
reviewed Approve Inserts/updates are extremely slow with Merge Replication in SQL Server 2008
Mar
24
answered Domain User lockout after SQL Cluster Failover
Mar
19
answered SQL Server: update trigger fires before insert trigger
Mar
19
comment SQL Server: update trigger fires before insert trigger
How about making the procedure where it writes to the logging table first, then the base table, if I understood your issue correctly.
Mar
19
comment Purging Data that has Foreign Keys
Would dropping the constraint for now work or is that too risky in the environment? Also, AFAIK you can partition with FKs as long as several requirements are met. tinyurl.com/n6yj38q
Mar
18
answered MongoDb Upgrade from 2.6 to 3.0 Issue
Mar
18
comment Consolidating 2,000+ databases into a single database with up to 20,000 concurrent users
@LiamWheldon based on TomToms input, you can probably forget a lot of the cpu thread and concurrency issues. If you can give us some more background on the table and usage patterns (read/write ratio, if it's succepitble to high/low fragmentation, etc.) we can give you a more detailed answer.
Mar
18
comment Consolidating 2,000+ databases into a single database with up to 20,000 concurrent users
@TomTom I hope so too, but since the title stated 20k connections per second I tried to make it very clear for him what that would entail.
Mar
18
revised Consolidating 2,000+ databases into a single database with up to 20,000 concurrent users
added 263 characters in body
Mar
18
answered Consolidating 2,000+ databases into a single database with up to 20,000 concurrent users
Mar
17
answered Separation of Duties - Can a DBA patch or Upgrade a SQL Server 2008 R2 DB without TDE Encryption keys?