Comments
Sort by recent activity
A Stored Procedure cannot begin a new line (or current line) after another statement (within a single batch) without using the EXEC keyword.
If you type in: SELECT * FROM myTable
EXEC ap_
you should get all the suggestions that match your input.
Mike / comments
A Stored Procedure cannot begin a new line (or current line) after another statement (within a single batch) without using the EXEC keyword.
If you type in:SELECT * FROM myTable
EXEC ap_
you shou...
Yes, you are correct, it does happen with Temp Tables and Table Variables.
Mike / comments
Yes, you are correct, it does happen with Temp Tables and Table Variables.
Mike
Tim,
I don't see that happening with SELECT * or INSERT INTO auto completion. Both types of auto-complete list all the columns in their natural table order.
I also don't see a setting to change that behavior either.
Mike / comments
Tim,
I don't see that happening with SELECT * or INSERT INTO auto completion. Both types of auto-complete list all the columns in their natural table order.
I also don't see a setting to change th...
The SQL Prompt 4 detailed version is 4.0.2.27.
SQL Server Management Studio Version is 9.00.3042.00.
Enter the following query in the msdb database in SSMS and then use the Tab key to expand the SELECT statement: SELECT sai.*
FROM [dbo].[sqlagent_info] sai
It used to (and should in my opinion) display as follows: SELECT sai.[attribute],
sai.[value]
FROM [dbo].[sqlagent_info] sai
but instead appears with brackets around the aliases: SELECT [sai].[attribute],
[sai].[value]
FROM [dbo].[sqlagent_info] sai
Mike / comments
The SQL Prompt 4 detailed version is 4.0.2.27.
SQL Server Management Studio Version is 9.00.3042.00.
Enter the following query in the msdb database in SSMS and then use the Tab key to expand the SE...
I tried your suggstion and it made no difference. The option was already unchecked. I tried both ways (checked and unchecked) and it still does not indent properly.
Mike / comments
I tried your suggstion and it made no difference. The option was already unchecked. I tried both ways (checked and unchecked) and it still does not indent properly.
Mike
Sent an email to RedGate Support as requested.
Mike / comments
Sent an email to RedGate Support as requested.
Mike
Despite the other posts regarding issues and functionality changes (or bugs) posted by myself and others, I think we all have noticed the speed/performance increase and the improved response time.
Thanks for these improvements!
Once we are able to work through a lot of these little issues (hopefully fairly quickly), I am sure this will become one of the best RedGate tools that help all of us database coders complete our work faster and more accurately! I know I use it constantly every day, all day long!
Mike / comments
Despite the other posts regarding issues and functionality changes (or bugs) posted by myself and others, I think we all have noticed the speed/performance increase and the improved response time.
...
MasterCephus wrote:
ok, all of my backup files are set to that as you said...but how do I automatically turn that off? That seems like a pretty rough manual process to have to go in there every day and uncheck the newly created backup files so they will be deleted when I want them to be deleted.
There is no way (that I know of) to prevent Windows from setting this flag when a file is created or modified.
However, you can run a command to remove that flag on an entire directory and all its subdirectories. Just put the following command in a batch file and run it on your desired schedule: attrib -A D:\DatabaseBackups\*.* /S /D
Mike / comments
MasterCephus wrote:
ok, all of my backup files are set to that as you said...but how do I automatically turn that off? That seems like a pretty rough manual process to have to go in there every...
MasterCephus wrote:
If that's right (which I am not doubting you, just talking out loud), then there is no way to naturally delete the local files that you create...so the FILEOPTIONS flag is meaningless without doing something manually...
I agree. I don't think that should be the proper behavior for the ERASEFILES Option. It should be left up to the User on how to keep/erase/backup etc the backup files according to their needs and/or requirements.
I just use a separate scheduled batch file job to delete the local files. Not the best option, but it works! Hopefully, RedGate will look into changing this functionality in future versions of the SQL Backup product.
Mike / comments
MasterCephus wrote:
If that's right (which I am not doubting you, just talking out loud), then there is no way to naturally delete the local files that you create...so the FILEOPTIONS flag is me...
MasterCephus wrote:
ok Setting FILEOPTIONS = 3 didn't work...in fact it didn't delete on local disk and on the network...
By reading what the FILEOPTIONS flag does, I have to think this has to be a bug...
If I set it to 1, it will delete the files from the network. Tonight I will run a backup with the flag set to 2 to see if it deletes the files from disk. If that works, then there should be no reason that 3 would not do both (from what the help file explained the flag).
I have the same situation on my system. Make sure the Windows OS Archive Flag is not set on the local system for the files. SQL Backup will not delete these files if the Archive Flag is set (even if the file meets the date time criteria).
Mike / comments
MasterCephus wrote:
ok Setting FILEOPTIONS = 3 didn't work...in fact it didn't delete on local disk and on the network...
By reading what the FILEOPTIONS flag does, I have to think this has to b...