Viewing 15 posts - 511 through 525 (of 2,387 total)
Once user has permissions to create table/view, He will be the owner of these objects and will be able to alter them.
February 11, 2004 at 7:11 am
CheckDB will tell your which tablea and indexs in trouble. Try to drop the indexes, run dbcc checktable and recreate the indexes.
February 10, 2004 at 1:47 pm
SELECT convert(varchar(3), DATEDIFF ( day , '01/01/2004' , getdate())) + '-' + convert(varchar(4), YEAR(getdate()))
February 10, 2004 at 1:22 pm
1. Isolate the machine in its own environment or network.
2. Configure instance of SQL Server not to listen for network protocols
3. Remove login "BUILTIN\Administrators".
But you have to trust...
February 10, 2004 at 10:08 am
According to the link Jonathan posted, you shouldn't adjust it.
As suggested in previous posts, You should look into whole system performace and try to identify the bottlenecks.
February 10, 2004 at 9:59 am
Create package and push to client machines.
SMS from Microsoft.
http://www.wise.com/products.asp from Wise Solution.
February 10, 2004 at 9:47 am
How large is your data? Either backup/restore and sp_detach_db/ sp_attach_db work. See BOL for details.
February 10, 2004 at 9:41 am
Do you see "The working thread limit of 255 has been reached" in SQL Server error log?
February 10, 2004 at 9:38 am
After rename your machine name, run setup and choose upgrade option.
The drop old name and add new name in SQL Server. Don't forget change the server name in sysjobs.
February 10, 2004 at 9:32 am
It is just informational message. I have it all the time once you right click the SQL Server and property. Ignore it.
February 10, 2004 at 9:16 am
The fix has newer version (878) of sqlserver.exe than what you have.
11-Nov-2003 20:34 2000.80.878.0 7,606,353 Sqlservr.exe
Call PSS at microsoft to get it. It should be free of charge.
February 10, 2004 at 9:14 am
What do you try to achieve? Instead shrink the database, you can shrink each files of the database once at a time.
February 10, 2004 at 9:10 am
If you want to change the location of SQL Server error log file, change it from properties --> general tab --> startup patameters.
February 10, 2004 at 9:04 am
I would make a little changes to your process at step1 and step8.
1. Shutdown SQL Server, backup all system MDF/LDF to somewhere.
8. Replace newly created system databases from the backup. You don't have to...
February 6, 2004 at 6:40 pm
Viewing 15 posts - 511 through 525 (of 2,387 total)