This white paper is a companion to the information about FILESTREAM found on TechNet. This paper delves deeply into selected topics that should be considered when implementing a solution that uses FILESTREAM, including design considerations, maintenance, and management of a FILESTREAM environment.
2011-05-24
3,306 reads
2011-05-23
12,948 reads
The PATINDEX function of SQL Server packs powerful magic, but it is easy to get it wrong. Phil Factor returns to the Workbench format to give a tutorial of examples, samples and cookbook ideas to demonstrate the ways that this underrated function can be of practical use. It is intended to be pasted into SSMS and used as a basis for experiment.
2011-05-23
5,331 reads
If you make the decision to upgrade to 2008, there are a number of tools that make the process easier, but you still need to understand what things you should consider. We have a new article from Arshad Ali to help you understand the process and what you should consider.
2011-05-20 (first published: 2009-03-02)
22,602 reads
Research firm The 451 Group coins "NewSQL" to categorize a new breed of database designed for distributed environments -- like the cloud.
2011-05-20
4,064 reads
Monitoring blocking can be problematic when you cannot catch it in the act. This article will show you an easy way to configure a SQL Server Profiler Trace to monitor blocking
2011-05-19
12,237 reads
SQL Server 2008 introduced many new functional and performance improvements for data warehousing, and SQL Server 2008 R2 includes all these and more. This paper discusses how to use SQL Server 2008 R2 to get great performance as your data warehouse scales up. We present lessons learned during extensive internal data warehouse testing on a 64-core HP Integrity Superdome during the development of the SQL Server 2008 release, and via production experience with large-scale SQL Server customers. Our testing indicates that many customers can expect their performance to nearly double on the same hardware they are currently using, merely by upgrading to SQL Server 2008 R2 from SQL Server 2005 or earlier, and compressing their fact tables. We cover techniques to improve manageability and performance at high-scale, encompassing data loading (extract, transform, load), query processing, partitioning, index maintenance, indexed view (aggregate) management, and backup and restore.
2011-05-19
5,175 reads
With each revision, SharePoint becomes more a SQL Server Database application, with everything that implies for planning and deployment. There are advantages to this: SharePoint can make use of mirroring, data-compression and remote BLOB storage. It can employ advanced tools such as data file compression, and object-level restore. DBAs can employ familiar techniques to speed SharePoint applications. Bert explains the way that SharePoint and SQL Server interact.
2011-05-18
3,334 reads
Service Broker is a great feature that allows you to defer processing in SQL Server. Learn how you can have processes work together, but in an asynchronous fashion in this piece from Gary Strange.
2011-05-17
10,927 reads
This white paper describes how to use database mirroring to increase the availability of the replication stream in a transactional environment. The document covers setting up replication in a mirrored environment, the effect of mirroring partnership state changes, and the effect of mirroring failovers on replication. In addition, it describes how to use LSN-based initialization to recover from the failover of a mirrored Subscriber database.
2011-05-17
3,504 reads
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...
By HeyMo0sh
In the realm of software development and content creation, the deployment pipeline serves as...
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