In your development environment if you have locked down permissions for developers, but still need them to execute stored procedures you will need to grant execute rights each time a new stored procedure is generated. In this tip I will show you a way of doing this automatically each time a new stored procedure is created without granting your developers additional permissions.
2009-11-13
3,474 reads
SQL Azure is very similar to traditional SQL Server and now supports many standard TSQL commands. This article demonstrates the use of TSQL commands to create SQL Azure objects.
2009-11-12
3,874 reads
In SQL Server 2008 one can store BLOBs (e.g. Images, video, Word, Excel, PDF, MP3, etc) in the NTFS file system rather than in a database file. This can be done by using the new FILESTREAM feature which was introduced in SQL Server 2008. In this tip we will take a look at some of the best practices which a database administrator can follow to get the best performance when using the FILESTREAM feature of SQL Server 2008.
2009-11-11
4,240 reads
FxCop is a useful tool for analyzing code to highlight potential issues and deviations from best practise. To fully utilize to power of FxCop, custom rules can be added to the inbuilt rules that ship with FxCop.
2009-11-10
1,639 reads
Recently, I was at a conference, and I heard the following discussion about what a data warehouse was. One person suggested that a data warehouse was really all the old legacy systems connected by software that could access the data. By calling such a contraption a data warehouse, the organization could avoid having to do the hard and complex work of integration. There are so many problems with this federated approach to a data warehouse that they are almost not worth repeating here. But (once again!) here goes.
2009-11-09
6,637 reads
The conclusion of our coverage of the Reporting Services component available in SQL Server 2005 Express Edition discusses systematizing the troubleshooting approach by focusing specifically on performance problems (as opposed to those impacting functionality).
2009-11-06
2,804 reads
That said, even though my personal focus is pretty much OO, I still miss stuff. SQL Server 2005 came out with the CROSS APPLY and OUTER APPLY operators and I have just started learning how to use APPLY in the last month or so. When I think I have it figured out, I am fortunate enough that some of you are interested in reading about my understanding of the technology.
2009-11-06
7,434 reads
We are storing large text and URLs that are over 900 bytes in some of our tables and have a requirement to enforce uniqueness in those columns. But SQL Server has a limitation that index size can't be over 900 bytes. How do I enforce uniqueness in these columns and is it possible to achieve this in SQL Server 2005 and above? What are my different options to solve this problem? I heard that we can use CHECKSUM to create a hash, but is it possible to avoid collisions in the hash value as we are storing millions of rows?
2009-11-05
3,006 reads
Loading EBCDIC data into SQL Server is not a well documented process - this article provides a very useful guide to optimizing the performance of this operation.
2009-11-05
2,019 reads
Query performance can be affected by many different factors. This article introduces another best practice of how and how not to use a function within your T-SQL statements.
2009-11-04
8,725 reads
By Steve Jones
This was Redgate in 2010, spread across the globe. First the EU/US Here’s Asia...
By John
Today is Christmas and while I do not expect anybody to actual be reading...
By Bert Wagner
Until recently, my family's 90,000+ photos have been hidden away in the depths of...
Comments posted to this topic are about the item SQL Server 2025 Backup Compression...
Comments posted to this topic are about the item The Large Encoded Value
Comments posted to this topic are about the item The Side Job
I want to use the new BASE64_ENCODE() function in SQL Server 2025, but return a string that isn't large type. What is the longest varbinary string I can pass in and still get a varchar(8000) returned?
See possible answers