I played with this compression CLR for SQL 2005 more than five years ago.

It worked at the time, but as Gail said, I think doing it in TSQL is...

As Sean has identified, all we can offer is vague advice unless ou have some details we can look at to try and help.

here's a quick list of some things...

nope, a database doesn't keep track of what references Itself, only what objects it's own objects references.

for same server references, you could query each database and stick the results into...

that's one of the advantages/disadvantages of Encrypt by PassPhrase:

you can prevent the DBA from getting to the data if he doesn't have the passphrase. By The Same Token, if you...

you could run into problems with inserting/updating rows with unecessarily oversized rows of data;

SQL still has a max row size of 8060, so if you had an update statement that...

as far as i know, it's not possible; without the pass phrase you'd have to try a dictionary attack on decrypting the values, and see if any if the encrypted...

The Service Broker or Extended Events both...

way too many assumptions and alternate technologies to even begin to offer much more than the basics.

1. you would need a web server, that also has access to where ever...

I believe when you call the procedure, you need to mark the parameter as output also:

exec Testout 'Y', @p2 OUTPUT

my first guess at what you are asking;

you mentioned hundreds of thousands, but your pattern only allows 99999 values.

note i'm still using an identity and a default value in order...

it kind of sounds like the client has your application already in place, and when they upgrade, they need to run scripts too?

I know in our case, we've done it...

i get this a lot when i use an explicit transaction, which i then role back; afterwards, in that situation i get the same error you reported when i then...

AndrewSQLDBA (4/1/2013)

---

Because that you can have more than one filegroup. And that tells SQL Server to create the object in a certain file group. Yes, it is required. That is,...

it's trivially ewasy, but the most important thing is to make sure noone has sysadmin rights; you cannot hide or deny access to a sysadmin.

sql is deny by default, so...

an example of what Gail was referring to:

USE [SandBox] --my db for users to do stuff.

CREATE ROLE [ReallyReadOnly]

--give my new role READ permission to ALL tables

EXEC sp_addrolemember N'db_datareader', N'ReallyReadOnly'

--explicitly DENY...