I have upgrade my SQL 2000 server OS to windows 2003 server . only UNC . There is no problem to access the map drives from windows 2003.Windows 2003 has much tighter security I would look there However it is a best practice NOT to use mapped drive letter referenced from SQL, and instead you SHOULD use UNC names Perhaps now is a good time to start using UNC names.
What is the best practice for installing SQL onto a SCSI Array? I have the OS on a RAID 0-1 Array and I have a RAID 5 Array for Data. Is it Best to Install SQL on the RAID 0-1 with the OS and put the DBASE on the RAID 5 or Install SQL with the database all on the RAID 5, seperate from the OS? Any info is appreciated. Thanks!For the ultimate in I/O throughput, assign each type of major I/O activity (database, log files, tempdb, etc.) to its own separate RAID controller and dedicated RAID array. Very expensive, but very fast. http://www.sql-server-performance.com/hardware_tuning.asp#I/O
I have a SQL Svr 2000 sp3 installation. We have multiple Jobs which are using ActiveX scripts to script out database objects on a nightly basis. Once in a while these jobs will fail the Agent's account? Also, have you checked Agent's log, SQL Server error log, Windows Event log? Maybe you could find out how to reproduce the error queued for the ActiveScripting subsystem Running the code manually works fine.Is this SQL Error or OS error? If this is OS error, you can get the following description using net helpmsg 208 command prompt command: The global filename characters, * or ?, are entered incorrectly or too many glob al filename characters are specified. If it is SQL
Need help on multiple language support in SQL Server 2000, I'm constructing a new db now I need some info on what the Collation should be set to, and also any other tip on this issue. I will be using Japanese, Polish and Swedish language.Hello, I cannot help on the Collation however I can give a good tip (if you didn't know already) that is use unicode nchar, nvarchr, ntext ect, although they take up a lot more space they are language independant. J the Collation should be using Japanese,
and Workgroup to 3GB. That would mean that 32 bit SQL 2005 Standard running on 32bit windows 2003 Enterprise can use max 32GB of RAM (minus 2-3 GB for OS). Right? But SQL 2005 BOL say that AWE is only supported in Enterprise and was the case (4GB limit) only when running 32bit SQL standard on x64 windows. Microsoft should really mention that since they are advertising SQL 2005 Standard everywhere like it has no RAM limit (only OS limit), when this is true only for IA64 edition was confusing which X you were referring to. 32bit SQL server on an X64 OS works as I mentioned. But if you are using the X64 edition of SQL Server 2005 database engine on an X64 OS then AWE is not required. I don'
I know ew can distribute backup files on multiple disks. is there a way to specify the size also ? to illustrate : my backup size is 105 GB. I want to specify to save xGB on Disk1 and rest on disk2 . Is it poosible ? Any hellp will be highly appreciatedon Reply: Opps on that last reply, you said backup files, and I was thinking database files. Sorry about that.
of thumb how or when to create an additional statistic on multiple columns. SQL Server already generates statistics for each field (_WA .). The Index Tuning Wizard suggests new indexes and also new statistics, sometimes on multiple columns. But I have no ideas where he finds following command: exec sp_dboption '[database name]', 'auto create statistics' With this setting on, SQL Server will create the statistics it needs at run time whilst running queries. If you've set it both columns in indexable expressions (where clauses). As far as where to find information on the optimizer's concerned, look up the following books: (a) Inside SQL Server 2000, by Kalen Delaney (MS Press) or (b) The Guru'