Viewing 15 posts - 136 through 150 (of 167 total)
Firstly run upgrade advisor to make sure all of your applications are going to be compatible with SQL 2008r2.
There are many things to consider when deciding on instances for consolidation,...
April 13, 2012 at 5:00 am
The DNS option (create a cname record to the new server, make sure you rename your old server as well:-) ) is a good shout also providing you named...
April 13, 2012 at 3:58 am
You can setup a SQL Alias using a .reg file, here is a sample keep in mind that its from a windows XP client so may need to be modified...
April 13, 2012 at 3:53 am
SQL Server Audit would be an option, this may help http://msdn.microsoft.com/en-us/library/dd392015(v=sql.100).aspx
April 11, 2012 at 2:48 am
Is the SQL Browser service running?
April 10, 2012 at 4:35 am
You can use SQL Aliases for this, we configure every SQL client using a standard .reg file that contains server\instance details, it doesn't cover every applications as there is stuff...
April 10, 2012 at 1:23 am
you can also export the trace definition to a .sql script and modify that in SSMS which may improve things also
April 4, 2012 at 2:55 am
ok, you are using the D$ share, you need to be an admin account to use that, I guess there is a trust between the 2x domains if domain administrator...
April 3, 2012 at 7:34 am
Are both the share level and NTFS permissions set to everyone full control?
April 3, 2012 at 6:38 am
Great artical John, i'm probably not alone in thinking why haven't I done that already 🙂 (implementing it in DEV as I type), looking forward to your next post.
Mike
April 3, 2012 at 3:43 am
42 = Answer to the question
April 3, 2012 at 2:01 am
ah, may have read that wrong sorry, are you looking for just the SQL Native Client, this can be installed just by running the sqlncli.msi from your installation media
April 3, 2012 at 1:50 am
you need client components - management tools
April 3, 2012 at 1:49 am
Viewing 15 posts - 136 through 150 (of 167 total)