Viewing 15 posts - 241 through 255 (of 313 total)
I know this is a 2005 forum, but you should look into policy-based management for SQL 2008- this would allow you to set up criteria and only allow objects with...
March 16, 2009 at 8:32 pm
In the properties of the script task, add the variable into the read/write variables list.
Putting User::variableName or just the variable name should work (provided you didnt change the namespace).
that will...
March 16, 2009 at 8:28 pm
In addition to the other posts, I would also make sure any logins you bring over from sql 2000, ensure that the password is either a strong password, or...
March 16, 2009 at 5:38 pm
After looking over the package configurations, this would probably be better for another situation, and was very useful.
However, I ran into issues with generalizing the location of the XML file...
March 2, 2009 at 11:24 am
Thanks for the suggestion! I'll take a look at package configurations. I haven't done too much with them. But I'm assuming i could loop through a list...
February 26, 2009 at 2:42 pm
this only seemed to generate "GRANT CONNECT" statements when I ran it.
Steve
February 6, 2009 at 12:44 pm
Ok cool. I mentioned that they'd still be able to stop SQL if they wanted, but figured it couldn't hurt to mention the builtin\administrators removal.
Take care,
Steve
February 5, 2009 at 12:55 pm
Madhu,
I think the points of some of the others posters aren't being heard.
By setting instance 1 on node 1 to use 12GB of RAM, you cannot expect a successful failover...
February 4, 2009 at 9:55 pm
The sysadmin will still be able to stop SQL SErver and delete files, but you should make sure that you remove the builtin\administrators group from being an administrator in SQL...
February 4, 2009 at 9:28 pm
RBarry,
Thought it might have just been my screen resolution. I fixed the tabs in there.
I did note that the script was "similar" except for database level instead of login...
January 31, 2009 at 7:43 pm
rick (1/30/2009)
January 31, 2009 at 6:34 pm
/*
This script will script the role members for all roles on the database.
This is useful for scripting permissions in a development environment before refreshing
development with a copy of production. ...
January 31, 2009 at 6:08 pm
Madhu,
Check out this URL:
It has a few recommendations for getting access to the single user connection that is allowed.
Two of the suggestions are:
1. Make sure SQL Agent is...
January 31, 2009 at 5:46 pm
I agree with the partitioning post. Lay out multiple disks, and separate the load of your largest tables across multiple filegroups containing multiple files.
For example:
Orders table has data from...
January 31, 2009 at 2:45 pm
As a previous poster briefly mentioned, check the Windows Environment Variables. By default it's set to the docs and settings folder. If anyone logs on to run a...
January 20, 2009 at 9:46 pm
Viewing 15 posts - 241 through 255 (of 313 total)