Viewing 15 posts - 586 through 600 (of 1,271 total)
I've helped out a few people in person with this problem, and every time it came down to there being some configuration that was wrong on their end.
My advice is...
May 13, 2009 at 11:32 am
The statement that "snapshots generally take seconds to drop and create" is accurate. The key is generally. There are cases where creating a snapshot can take a very long time....
May 13, 2009 at 9:56 am
Just a side note, but starting with SQL 2005, there is a system procedure that will do this for you: xp_create_subdir
Yet another reason to consider upgrading. 😀
May 8, 2009 at 11:32 am
Krishna Potlakayala (4/18/2009)
Sam Shiell (4/18/2009)
we don't need a full-time dba".OWssssss... You are going to hurt your SQL servers, which is your data, which is your business.:-D
I think when...
May 8, 2009 at 11:14 am
Thanks for pointing out the 2 DMV's!! If someone wanted to run this script automatically across all servers in their environment to find the clustered servers and collect information about...
May 8, 2009 at 10:44 am
Erode P. Satheesh (5/7/2009)
The problem is with ServerB/Instance02 to speak with...
May 7, 2009 at 10:57 am
This is going to be a huge performance hit to your application. You should avoid extra round trips to the database and do the validation on the client side. If...
May 6, 2009 at 11:12 pm
When I encountered this error, it was because I installed SQL on a system that uses User Access Control (Vista, Windows 2008), and I did not run the install as...
May 6, 2009 at 11:04 pm
Probably, you are not sysadmin and the public user in the model database is disabled. You need to have someone who is a sysadmin correct this. They either need to...
May 6, 2009 at 10:52 pm
I agree completely with everything Andrew said. This is the best practice and should be standard for any well organized and properly staffed place.
May 5, 2009 at 10:14 am
What do you mean by "losing the transaction"? If you mean that it won't be getting hit with live data, that is correct and no there is no elegant way...
May 4, 2009 at 2:32 pm
Backup and restore is the most commonly used technology. Backup production, restore it to staging/QA, run your scripts/rollout process, and test. If all looks okay, repeat the rollout in production.
May 4, 2009 at 2:24 pm
Krishna is correct. No form of high availability allows you to modify the schema on the secondary/offline database. There is a very limited amount of changes you can do with...
May 4, 2009 at 2:09 pm
The functionality you describe can be found in SQL Reporting Services. Otherwise, you have to build your own front end display that interprets the data.
May 4, 2009 at 12:29 am
Viewing 15 posts - 586 through 600 (of 1,271 total)