Viewing 15 posts - 21,331 through 21,345 (of 22,219 total)
So far we only three or four schema per database. We manage our security through a role in the database. The roles get access to stored procedures. The stored procedures...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 5, 2008 at 5:57 am
BOHICA
:w00t:
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2008 at 11:24 pm
To my knowledge, not using this quick way of scripting. If you do an actual export to file you get the option of having a single file or seperate files...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2008 at 11:10 am
I'm not sure what you mean. We're not talking about tables, but about stored procedures. If you have a data type of int in the stored procedure, the character length...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2008 at 11:06 am
This isn't documented, but does what you want:
exec sp_procedure_params_rowset 'procname'
The -1 returned by the view is the designed method. The procedure, in my mind, is worse. It shows a length...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2008 at 10:28 am
Personally, I use autogrow. But, I recognize that it is a crutch. I spend a lot of time & effort in setting up monitoring so that I know how much...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2008 at 9:41 am
SELECT * FROM INFORMATION_SCHEMA.PARAMETERS
WHERE SPECIFIC_NAME = 'myproc'
That'll get you exactly what you want
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2008 at 9:36 am
I agree, if you have no information on anticipated load, etc., about 25% of the initial data size would be a prudent number.
However, I'd make sure I had a more...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2008 at 8:45 am
Just remember that short-hand notation like BTW, OTOH, IIRC, are for very informal communication. You can use them on line, but you wouldn't want them in formal documentation, requests for...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2008 at 6:58 am
PASS is the Professional Association for SQL Server. They have an annual get together called the PASS Summit. This year it will be in November in Seattle. They also have...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2008 at 6:15 am
You want to take a look at the catalog views, like sys.database_files which will give you hard information about the files themselves, or dynamic management views, like sys.dm_db_file_space_usage which will...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2008 at 6:09 am
Because we like our data
😀
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2008 at 6:02 am
More detail would be needed to provide useful answers. Does merge mean two identical structures but different data, two completely different structures but similar data, two totally different structures and...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2008 at 6:00 am
We've gone both ways. If you do leave the hyperthreading on, you can't treat it like a real multi-core machine. So for example we have two processor machines with hyperthreading,...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2008 at 5:56 am
What about using a SCHEMA? Then you'd see the list like this:
Module1.Table1
Module2.Table2
Etc. Then you can use the Filter function in SSMS to only display the schema that you're interested in.
Another...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
January 4, 2008 at 5:50 am
Viewing 15 posts - 21,331 through 21,345 (of 22,219 total)