Viewing 7 posts - 1 through 7 (of 7 total)
The script exports everything just fine, but however when I run it on the other users machine it just copies the groups and not the machines. I manually copied the...
April 6, 2006 at 7:54 am
Out of curiosity. I thought that instances were only used under SQL Enterprise Edition. Apparently I was mistaken. Can you install extra instances on a SQL 2000 standard box without...
October 28, 2005 at 9:59 am
The simplest solution to this problem, and not neccessarily the most elegant is to copy the stored procedure sp_helpdb into a new stored procedure called something like sp_helpdbname. Once you...
September 26, 2005 at 8:01 am
I have also installed SQL server to several different VMWare systems. We ran test systems on VMWare for about 6 months and have had production running on VMWare for about...
September 8, 2005 at 8:48 am
From my experience SQL 2000 does not balance itself evenly between the processors. Nor does Server 2003 balance itself well.
However if you are running on a 2003 platform and are...
September 8, 2005 at 8:43 am
No, we are running on 2003 Enterprise Edition. Our SQL version is 2000. Like I said, we never had this problem until the laterst server patches were applied.
November 16, 2004 at 7:59 am
I would try attaching the DB using a single file
exec sp_attach_single_file_db 'dbname',
'pathname\dbname_data.mdf'
This will create a new log file so you will need to rename your old log file.
November 15, 2004 at 1:52 pm
Viewing 7 posts - 1 through 7 (of 7 total)